Delegation: the parent must match your zone

Published September 4, 2026. Updated September 9, 2026.

Your domain is delegated: the registry (the parent zone, e.g. .com) publishes the set of nameservers that are authoritative for your domain. Those nameservers then serve your actual records. The two must agree.

What the report checks

Delegation found: the parent hands your domain to nameservers at all.
Parent vs child NS: the NS set the parent publishes matches the NS set your own nameservers publish for the zone. A mismatch (a nameserver listed at the parent but not in the zone, or the reverse) causes intermittent failures, because resolvers may use either list.
Consistency: all of your nameservers return the same NS set.

Why a mismatch is a problem

Resolvers cache and use the parent's list, but your zone's own list is authoritative. If they differ, some lookups go to a server that no longer serves the zone (or misses a working one), so the domain works "sometimes."

What if there's no delegation at all?

Sometimes the report says the domain does not appear to exist because the parent (the registry) returns no delegation for it, even though whois shows the domain registered with nameservers. Those are two different things: whois is the registration record; the delegation is the NS records the registrar has to push into the registry's zone. You can have the first without the second, and until the registry actually publishes the delegation, resolvers never learn which nameservers to ask, so the domain is unreachable no matter how well your DNS host is configured.

Common reasons a registered domain has no delegation:

Just registered, or the nameservers were just changed. The registry delegation has not propagated yet - usually minutes, occasionally up to a day or two.
The registrar never pushed the nameservers to the registry. You set them in the registrar's panel but the change was not actually submitted (an unfinished step or a registrar-side hiccup).
A hold on the domain. serverHold / clientHold, an unverified ICANN registrant email, or an expired / redemption-period domain all make the registry pull the delegation while whois still shows the domain.
A billing or compliance problem. Non-payment or a compliance flag can suspend the delegation.

Why the registrar is the right place to go: the delegation lives in the relationship between your registrar and the registry - not with your DNS or hosting provider. Only the registrar can (re)submit the nameservers to the registry, lift a hold, or clear a verification or billing flag. Your DNS host can serve the zone perfectly and it still will not help until the registrar has the delegation published. So when there is no delegation, contact the registrar first (confirm the nameservers are set and submitted, and that the domain has no hold or unverified-email suspension), not the DNS or hosting provider.

How to fix it

Decide on the correct list of nameservers, then make three places agree: the registrar's delegation (the parent), and the NS records inside your zone on every nameserver. Change them together and allow for TTLs to expire.

How to verify

# What the parent (registry) says:
dig com. NS example.com +norecurse @a.gtld-servers.net
# What your own nameservers say:
dig example.com NS +norecurse @<your-nameserver>

The two NS sets should be identical.