Topic · DNS & Infrastructure
Authoritative DNS server
An authoritative DNS server serves official records for a zone rather than merely caching external responses.
How it works
Delegation records lead recursive resolvers to the authoritative servers that answer questions for the managed namespace.
What can go wrong
Editing records at an inactive DNS provider has no production effect when delegation points elsewhere.
What to check or do
Identify the authoritative NS set before modifying SPF, DKIM, DMARC or BIMI records.
How to investigate Authoritative DNS server
- Signal to investigate
- Two authoritative name servers return different DMARC TXT records.
- Evidence to collect
- Query every delegated NS directly and compare SOA serials, record values and DNSSEC signatures.
- Common wrong conclusion
- A recursive resolver returning a value does not prove all authoritative servers agree.
How to interpret the evidence
Partial deployment or failed zone transfer can create inconsistent results. Depending on resolver selection, customers may see intermittent SPF or DKIM validation failures.
What to change and how to verify it
Correct replication and delegation, confirm all authoritative nodes agree, then allow cached stale data to expire.
Put this into practice
Run a focused check, then explore protection if your domain needs it.