Skip to content
AdminKit

DNS NOTIFY

What is DNS NOTIFY?

DNS NOTIFY, defined in RFC 1996, lets a zone's primary nameserver immediately tell its secondaries the zone changed, instead of every secondary waiting out the SOA record's refresh timer to notice. AdminKit's zone-transfer guide explains what a secondary actually does once a NOTIFY message wakes it up.

By AdminKit team, Netbase JSC · Updated

DNS NOTIFY, defined in RFC 1996 (document record at the IETF Datatracker), lets a zone’s primary nameserver proactively tell its secondary nameservers that the zone has changed, instead of every secondary waiting out the SOA record’s refresh interval before checking again. Without NOTIFY, a secondary only polls the primary’s SOA serial number on a fixed timer — often tens of minutes to hours — so a zone change doesn’t reach secondaries until the next scheduled poll, even if the primary updated moments after the last one. With NOTIFY, the primary sends a small message to each configured secondary immediately after a change, prompting it to check the SOA serial right away rather than waiting; the secondary still compares serial numbers itself before pulling a zone transfer, so a NOTIFY message is only a wake-up signal and isn’t trusted blindly to mean new data is actually available. This shortens real-world propagation time for a zone update from however long the refresh interval happens to be down to roughly the time it takes to send one message and complete the resulting transfer, which is why most authoritative DNS server software sends NOTIFY by default whenever a zone’s serial number increases. BIND 9’s notify option is a concrete example: set to yes by default, it sends NOTIFY messages when a zone the server is authoritative for changes, to the servers listed in the zone’s NS records (except the primary named in the SOA MNAME field) and to any servers listed in also-notify. PowerDNS’s documentation on primary operation describes the same flow from the secondary’s side: secondaries react to a notification by querying the primary to see if the zone changed, and transfer its contents if it has. NOTIFY’s own message opcode is one of the values listed in IANA’s DNS Parameters registry, alongside ordinary query and update opcodes. The transfer that follows is usually an IXFR, carrying only the changed records, rather than a full AXFR.

NOTIFY vs. waiting for the refresh timer:

  • Without NOTIFY: a secondary only checks for changes on its own fixed refresh timer.
  • With NOTIFY: the primary wakes secondaries up immediately after a real change.
  • Either way, the secondary still verifies the serial number itself before pulling a transfer.

AdminKit groups dNS NOTIFY under its DNS cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What does DNS NOTIFY let a primary nameserver avoid?

Waiting for every secondary to poll the SOA record's refresh interval on its own fixed timer before noticing a zone changed.

Does a secondary trust a NOTIFY message blindly?

No -- it still compares SOA serial numbers itself before pulling a zone transfer; NOTIFY is only a wake-up signal, not proof that new data is available.

What kind of transfer usually follows a NOTIFY message?

An IXFR, carrying only the changed records, rather than a full AXFR.

What happens to propagation time once NOTIFY is in use?

It shortens from however long the refresh interval happens to be down to roughly the time it takes to send one message and complete the resulting transfer.