Topic · DNS & Infrastructure
DNS delegation mismatch
A DNS delegation mismatch occurs when parent-zone nameserver referrals disagree with the servers or records actually serving the child zone.
How it works
Resolvers follow parent NS and glue information, then query the delegated authoritative nameservers.
What can go wrong
Missing or incorrect delegation can make email authentication records intermittently unreachable.
What to check or do
Compare parent NS sets, child NS sets, glue records and DNSSEC status before editing records.
Practical scenario
After an email domain changes DNS provider, the registrar points to the new nameservers while the child zone still advertises an old server set. Some resolvers obtain current DKIM keys; others hit stale or unreachable authorities.
Verification checklist
- Query NS records at the parent delegation.
- Query each child authoritative server directly for NS and critical TXT records.
- Check glue and DNSSEC chain validity.
- Coordinate nameserver and DS changes with the provider before cutover.
How to investigate DNS delegation mismatch
- Signal to investigate
- Registrar delegation points to different servers than the DNS host being edited.
- Evidence to collect
- Compare registry NS with hosted-zone NS and query each active authoritative endpoint.
- Common wrong conclusion
- A green dashboard status in the new provider cannot override incorrect parent delegation.
dig +trace NS example.comEducational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.