DNS delegation: where it actually lives

Delegation is the record that connects your domain to its nameservers — and it is stored one level ABOVE you. For example.com, the delegation lives in the .com zone, published by your registrar. Your own zone repeats the NS records, but when the two disagree, resolvers walk down from the parent: what the parent says is what the world follows first.

To read the delegation where it actually lives, ask a nameserver of the PARENT zone, with recursion off:

dig @a.gtld-servers.net example.com NS +norecurse
# ou veja o caminho inteiro:
dig example.com NS +trace

Why this distinction matters

Because it explains the classic migration accident. You change nameservers at the registrar and the new zone is missing records: the domain breaks, and no amount of fixing the OLD provider helps — the parent already points elsewhere. The safe order is always: build the complete zone at the new provider first, verify it answers, then change the delegation.

It also explains why a freshly delegated domain can look "down" from one network and fine from another: resolvers cache the old delegation for its TTL, often 48 hours at the registry. The change is not propagating "through the internet" — caches are simply expiring at different times.