Topic · DNS & Infrastructure
DNS authoritative inconsistency
Authoritative DNS inconsistency occurs when nameservers for one domain return materially different answers to the same query.
How it works
A resolver may reach any delegated authority and receive a different record depending on synchronization or configuration.
What can go wrong
Intermittent DKIM or SPF failure can result even when one testing resolver appears correct.
What to check or do
Query every delegated authoritative server directly for critical mail-related names and compare answers.
Practical scenario
Three authoritative nameservers host a mail domain, but one misses the latest DKIM TXT value. Receivers choose different authorities and see intermittent DKIM lookup failures after a key rotation.
Verification checklist
- Enumerate every authoritative nameserver from the parent zone.
- Query selector TXT and other security records directly on each server.
- Compare SOA serials, RRSIGs and response codes.
- Correct synchronization before deleting old signing keys.
How to investigate DNS authoritative inconsistency
- Signal to investigate
- One nameserver returns old SPF while another returns the new policy.
- Evidence to collect
- Query all authoritative nameservers individually and compare complete RRsets and serials.
- Common wrong conclusion
- Successful tests against a single DNS resolver can conceal split publication.
dig @ns1.example.net example.com TXT
dig @ns2.example.net example.com TXTEducational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.