Topic · DNS & Infrastructure
DNS zone delegation
DNS zone delegation assigns authority for a child namespace to its own authoritative nameservers.
How it works
Parent-zone NS records establish the delegation, optionally with supporting glue records where needed.
What can go wrong
A delegated _domainkey or campaign subdomain can be changed by a vendor outside the central DNS team’s review.
What to check or do
Record delegation owners, monitor changes and use least-privilege DNS controls for vendor-managed zones.
How to investigate DNS zone delegation
- Signal to investigate
- An owner edits the expected DNS provider, but the public domain keeps returning older records.
- Evidence to collect
- Check the NS records at the parent zone and query the nameservers actually delegated by the registry.
- Common wrong conclusion
- Editing a DNS dashboard that is not authoritative for the domain cannot change public answers.
How to interpret the evidence
Registrar delegation and in-zone NS records are related but distinct. Mismatched glue or stale delegation creates outages that look like caching failures.
What to change and how to verify it
Reconcile registrar NS, authoritative zone and required glue; query each delegated server after the change.
Put this into practice
Run a focused check, then explore protection if your domain needs it.