Skip to content
Inspect My DNS

DNS delegation troubleshooting: authoritative disagreement vs propagation

When a domain answers differently depending on where you ask, there are two very different explanations, and only one of them gets better by waiting. This page explains how to tell them apart: by comparing what the parent zone says about the domain with what each of its authoritative nameservers says, one at a time.

What a delegation is

The parent zone — the registry for .com, .org or your country code — does not hold your records. It holds a referral: the set of NS records naming your nameservers, plus glue addresses where those nameservers live inside your own zone. Every resolver starts there. Each nameserver in that set then holds its own copy of the zone and is expected to answer with authority (the AA flag) and to agree with the others.

A delegation is healthy when the parent and the zone name the same nameservers, every one of them answers authoritatively, and they all serve the same version of the zone.

Propagation and disagreement are different problems

Cached propagation is resolvers still holding an answer they fetched before you made a change. Every authoritative server already gives the new answer; the old one lives in caches until its TTL expires. Nothing is broken, and it resolves itself — usually within the record’s TTL, and for a nameserver change within the parent’s NS TTL, often a day or two.

Authoritative disagreement is the authoritative servers themselves giving different answers, or the parent naming servers the zone does not. That never heals with time, because nothing is cached: a resolver that happens to pick the wrong server gets the wrong answer every time it asks. It shows up as intermittent failures that look exactly like propagation, which is why it so often goes unfixed for weeks.

The test that separates them is to skip the caches: ask each authoritative server directly, with recursion off. If they all agree with each other and with the parent, any difference you see elsewhere is caching. If they do not, waiting will not help.

Example: the parent referral against each nameserver

Synthetic example, for illustration only. example.com and the .example hosts are reserved names and the addresses are documentation ranges — this is not any real domain’s data. It shows the shape of what a report compares.

Synthetic comparison of the parent referral and each nameserver’s answers for example.com
AskedAuthoritative (AA)NS set it reportsSOA serialA for example.com
Parent referral (the registry for com.)No — a referral, as it should bens1.dns-host.example, ns2.dns-host.example, ns1.old-host.example——
ns1.dns-host.exampleYesns1.dns-host.example, ns2.dns-host.example2026111901192.0.2.10
ns2.dns-host.exampleYesns1.dns-host.example, ns2.dns-host.example2026110402198.51.100.7
ns1.old-host.exampleNo — REFUSED———

Read row by row, this delegation has three separate faults, none of them propagation, and one thing worth confirming:

  • A lame delegation. The parent still lists ns1.old-host.example, a former provider that now refuses the query. Resolvers that try it first time out or fail over. How to fix a lame delegation.
  • A nameserver mismatch. The parent names three servers; the zone names two. Which set a resolver ends up trusting depends on which it saw last. Registry and zone nameserver mismatch.
  • Serial drift. ns2 reports an older SOA serial than ns1, and a different address for the apex: zone transfers to it have stopped, so half of all lookups get stale data. Why SOA serials must agree.
  • Glue, if the nameservers move in-zone. None of these nameservers is inside example.com, so no glue is needed. Rename them to ns1.example.com and the parent must also hand out their addresses, or nobody can reach them. How glue records work.

A propagation delay would look different: every authoritative row identical, the parent agreeing with them, and only recursive resolvers out of date.

Checking it by hand

dig with +norecurse asks one server and only that server. First the parent — find a server for your TLD with dig NS com. — then each nameserver it names:

dig +norecurse @<a server for your TLD> example.com NS
dig +norecurse @ns1.dns-host.example example.com SOA
dig +norecurse @ns2.dns-host.example example.com SOA

Look for the aa flag in each answer, the same NS set everywhere, and the same serial on every server. Repeat over TCP (+tcp) and for every IPv4 and IPv6 address each server has: a server reachable on one address and not another is a fault only some resolvers will see.

Run the full report on a domain

The report does this comparison for you — the parent referral against every nameserver, over UDP and TCP, on every address — as part of all 62 checks. There is no separate delegation test: entering a domain runs the full report.