DNS Nameserver Sync & SOA Serial Checker
Perform real-time queries against all authoritative nameservers of a domain. Compare SOA serial numbers, MNAME master records, and identify zone replication lag between primary and secondary nameservers.
Why Authoritative DNS Synchronization Is Critical
In multi-nameserver deployments (Primary/Secondary BIND or hidden master setups), changes made to DNS zone files must propagate swiftly to all secondary nameservers using NOTIFY (RFC 1996) and AXFR / IXFR zone transfers (RFC 5936).
The SOA Serial Number Convention
The SOA Serial Number indicates the revision of the DNS zone. Whenever records are added or updated, the serial number MUST be incremented (typically using the YYYYMMDDnn format, e.g. 2026082101).
Common Causes of SOA Desynchronization
- Forgot to Increment SOA Serial: Secondary servers will assume the zone has not changed and will not request an incremental zone transfer (IXFR).
- Firewall / ACL Blocks on TCP Port 53: Zone transfers require TCP port 53; if blocked, secondary servers cannot sync updated records.
- TSIG Key Mismatch: Transaction Signatures (TSIG) authentication failure between primary and secondary nameservers.