Name servers & SOA · Lesson 7 of 8 · 3 min read
Troubleshooting delegation problems
Tools
dig +trace www.example.com # follow the delegation from the root
dig NS example.com @a.gtld-servers.net +norecurse # parent's view (referral)
dig NS example.com @ns-1234.awsdns-12.org +norecurse # child's own NS (look for aa)
dig SOA example.com @ns-1234.awsdns-12.org # does this server answer authoritatively?
for ns in $(dig NS example.com +short); do echo "$ns: $(dig +short SOA example.com @$ns)"; done # serial consistency
Symptoms and causes
| Symptom | Likely cause |
|---|---|
| New hosted zone created, domain still resolves via old DNS | Registrar still lists old name servers |
| Domain stopped resolving after recreating the hosted zone | New zone has new NS; registrar not updated |
| SERVFAIL from some resolvers only | Lame delegation (some NS don't serve the zone), unreachable name servers, or DNSSEC mismatch (DS at registrar doesn't match the zone's key) |
| Different answers from different authoritative servers | Serial not bumped (BIND), failed transfers, or multi-provider data out of sync |
Resolution fails or loops for a zone using ns1.<itself> |
Missing glue at the registrar |
| Subdomain delegation "doesn't work yet" | Cached NXDOMAIN/old NS; NS record in parent has a typo |
| Intermittent slow lookups | One of the NS is down/lame; resolvers time out before trying others |
| Secondary stopped answering after an outage | SOA EXPIRE reached without contacting the primary |
Enlarge diagram
Swipe sideways to see all of it, or tap to open it full screen.