@yousra if we define a block like this at node level:

In addition to this change, we also need to reuse our dedicated IP address for e-mails:

Best short-term solution, to allow mail from Docker services too, is to allow the new router IP.

Qwen3.8-Max insights: https://chat.qwen.ai/s/87951950-46a3-4e64-a2af-60f51458a089?fev=0.2.82

Actually there are 2 formats serial accepted :

• YYYYMMDD (8 digits)
• YYYYMMDDNN (10 digits)

Added verification of SOA serial format

Moved DNS validation scripts to _tests/roles/python/dns/ for better organization.

Was initially caught by kzonecheck after deployment of the zone file, and before reloading knot.

Configured at OVH level.

Next: reconfigure DNS zone in HE control panel, as it only has our IPv4.

DNS server listens correctly to IPv6:

Dorian and me retested the configuration this Monday evening, with the same findings.

So it's definitely ns1.he.net, because if I put slave.dns.he.net the TCP connection isn't established:

Claude Sonnet artifacts

I think configuration could actually be nice but I forgot in D3766 to bump the serial. Let's check (and do a test to detect that).

Dorian and me meet this evening to do the switch.

Not spot anymore. Python 3.11 is used on every FreeBSD systems now.

Closing as a duplicate, as with T1217 task, automation is there:

• new records can be submitted as a commit against zone file
• new zones can be added by creating a new file and pillar entry