Primary Name Server Not Listed At Parent

Site: fabulang.netlify.app
Domain: fabulang.com
DNS: Netlify

DNS health check shows error:

Primary Name Server Not Listed At Parent
dns1.p01.nsone.net

It also shows errors:

Name Servers are on the Same Subnet
198.51.44
198.51.45

SOA Serial Number Format is Invalid
dns1.p09.nsone.net 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 fabulang.com NS +trace | tail -n 6
fabulang.com.		3600	IN	NS	dns2.p09.nsone.net.
fabulang.com.		3600	IN	NS	dns3.p09.nsone.net.
fabulang.com.		3600	IN	NS	dns4.p09.nsone.net.
fabulang.com.		3600	IN	NS	dns1.p09.nsone.net.
;; Received 130 bytes from 198.51.45.73#53(dns4.p09.nsone.net) 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 mydomain.se SOA returns dns1.p01.nsone.net

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

dns1.p04.nsone.net
dns4.p04.nsone.net
dns2.p04.nsone.net
dns3.p04.nsone.net

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 example.com NS
example.com. 82218 IN NS b.iana-servers.net.
example.com. 82218 IN NS a.iana-servers.net.

and:

$ dig +noall +answer example.com SOA
example.com. 1034 IN SOA ns.icann.org. noc.dns.icann.org. 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.