Send NOTIFY to DNS secondaries #374

Open
opened 2026-06-12 13:18:25 +02:00 by felixalb · 2 comments
Owner

Some friend organizations (NVG, NTNU, Uninett) mirrors/slaves our DNS configurations. Currently, we allow TRANSFERs/axfr from them, so they can fetch, copy and serve entire zones for us.

However, when we update records, instead of waiting for TTL expiry, we can proactively push updates to their DNS servers with NOTIFY, so they immediately get the new zones. Read the nsd documentation, write some notify config, test and push to https://git.pvv.ntnu.no/Drift/PVV-DNS.

The relevant configuration should probably go somewhere near https://git.pvv.ntnu.no/Drift/PVV-DNS/src/branch/main/nsd.conf.nix#L42

Some friend organizations (NVG, NTNU, Uninett) mirrors/slaves our DNS configurations. Currently, we allow TRANSFERs/axfr from them, so they can fetch, copy and serve entire zones for us. However, when we update records, instead of waiting for TTL expiry, we can proactively push updates to their DNS servers with NOTIFY, so they immediately get the new zones. Read the nsd documentation, write some notify config, test and push to https://git.pvv.ntnu.no/Drift/PVV-DNS. The relevant configuration should probably go somewhere near https://git.pvv.ntnu.no/Drift/PVV-DNS/src/branch/main/nsd.conf.nix#L42
felixalb added the enhancementdns labels 2026-06-12 13:18:25 +02:00
felixalb added this to the Kanban project 2026-06-12 13:18:54 +02:00
oysteikt moved this to Medium priority in Kanban on 2026-06-21 17:46:54 +02:00
Author
Owner

This looks to be more important than I first thought, unless NTNU recently changed something?

felixalb@mirage:~$ dig +short @dvask.pvv.ntnu.no CNAME login2.pvv.ntnu.no
mirage.pvv.ntnu.no.
felixalb@mirage:~$ dig +short @ns1.ntnu.no CNAME login2.pvv.ntnu.no
drolsum.pvv.ntnu.no.
felixalb@mirage:~$ dig +short @1.1.1.1 CNAME login2.pvv.ntnu.no
mirage.pvv.ntnu.no.
felixalb@mirage:~$ date
Thu Jul 30 09:56:46 AM CEST 2026

NTNU NS1 has not updated to use de96a66351 that was over 12 hours ago, and our TTL looks to be 1 hour:

TTL = 60 * 60;

This looks to be more important than I first thought, unless NTNU recently changed something? ``` felixalb@mirage:~$ dig +short @dvask.pvv.ntnu.no CNAME login2.pvv.ntnu.no mirage.pvv.ntnu.no. felixalb@mirage:~$ dig +short @ns1.ntnu.no CNAME login2.pvv.ntnu.no drolsum.pvv.ntnu.no. felixalb@mirage:~$ dig +short @1.1.1.1 CNAME login2.pvv.ntnu.no mirage.pvv.ntnu.no. felixalb@mirage:~$ date Thu Jul 30 09:56:46 AM CEST 2026 ``` NTNU NS1 has not updated to use https://git.pvv.ntnu.no/Drift/PVV-DNS/commit/de96a66351cac7de0c216e2b7896a2f5f3978462 that was over 12 hours ago, and our TTL looks to be 1 hour: https://git.pvv.ntnu.no/Drift/PVV-DNS/src/commit/de96a66351cac7de0c216e2b7896a2f5f3978462/pvv-domain.nix#L15
Author
Owner

Now, it is at least updated. Propagation took between 12.5 and 16.9 hours this time.

Now, it is at least updated. Propagation took between 12.5 and 16.9 hours this time.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drift/issues#374