Primary Name Server Not Listed At Parent

DNS: Netlify

DNS health check shows error:

Primary Name Server Not Listed At Parent

It also shows errors:

Name Servers are on the Same Subnet

SOA Serial Number Format is Invalid reported Serial 1686607871 : Suggested serial format year was 1686 which is before 1970.

What can be done about this?

1 Like

HI @VirgilThinks,

Thanks for reaching out and welcome to Netlify’s Support Forums!

Did you make any changes? I do show that you are correctly configured with Netlify’s name servers:

dig NS +trace | tail -n 6		3600	IN	NS		3600	IN	NS		3600	IN	NS		3600	IN	NS
;; Received 130 bytes from in 8 ms

Visiting your site, it resolves properly. Are you seeing any errors?

Thanks. Yes it is resolving properly, it just worried me that the DNS health check issues a big warning about it not being listed at the parent! Do you understand why this is?

I have a few sites (other account) with Netlify and the others don’t have this error.

We are also seeing this warning when doing health checks.

dig SOA returns

But when configuring DNS for ny domains, it told me to add

So p01 is not in the list. Is this expected?

The SOA record often does not have the same name server domain name as the actual NS records for the domain. For example:

$ dig +noall +answer NS 82218 IN NS 82218 IN NS


$ dig +noall +answer SOA 1034 IN SOA 2022091310 7200 3600 1209600 3600

Note, that domain above isn’t using NS1 or Netlify DNS and I used it only to illustrate that it is common and acceptable for such a mismatch to occur.

SOA records are primarily used for zone transfers and Netlify doesn’t support zone transfers at this time. To summarize, the mismatch on the name server name can exist but when it does is should also be a non-issue.