Delegation and External Nameservers
July 16, 2026 ยท View on GitHub
This is a general DNS chapter. It assumes the registration platform has already been given the external authoritative nameserver hostnames.
Three Views of the Same Domain
Registration view
Stores the intended authoritative nameserver hostnames.
Parent DNS view
Publishes the delegation that resolvers actually follow.
Child authoritative view
Publishes the zone's SOA, NS, and ordinary resource records.
All three must be consistent enough for resolution to work.
Check the Delegation
dig NS example.dpdns.org
The returned nameservers should match the external DNS service's assigned set.
Trace the path:
dig +trace NS example.dpdns.org
The trace helps distinguish a parent delegation problem from a child-zone problem.
Check the Child Zone Directly
dig @ns1.dns-service.example SOA example.dpdns.org
dig @ns1.dns-service.example NS example.dpdns.org
An authoritative server must publish the zone before waiting for caching can help.
Delegation Failure Patterns
| Result | Likely layer |
|---|---|
| Parent points to old NS hostnames | Registration or parent delegation |
| NS hostnames are correct but time out | External authoritative service or network |
| One nameserver answers and another does not | External DNS synchronization or availability |
| SOA says the zone does not exist | Zone missing at external DNS service |
| NS works but A record is empty | Ordinary record missing from external DNS zone |
Do Not Mix Fields
Nameserver field: ns1.dns-service.example
A record value: 192.0.2.10
CNAME value: another-host.example
Resolver address: an IP configured on a client
Each belongs to a different context.
Evidence Worksheet
Record:
Expected external nameservers:
Observed delegated nameservers:
SOA answer from nameserver 1:
SOA answer from nameserver 2:
Time checked in UTC:
Next action:
Continue to DNS Record Types.