Skip to main content

Two Domain names on the same server, with near identical setup - but one says Primary nameserver not listed at Parent

martin MHC
We have a WHM server used as an email and domain server with its own DNS. One domain name was checked on MXToolbox and was stated as " Primary Name Server Not Listed At Parent " and "Local NS list does not match Parent NS list" . This domain will be referenced as Domain One. However, upon checking another domain name (referenced as Domain Two) on the same server this came back absolutely fine. Checking the DNS records via the DNS Zone Manager for both domains they are virtually identical (see below for differences). Both domains have the same NS records and the same " XXX.XXX.XXX.XXX.in-addr.arpa.Domain" Root Domain Reference records. Both domains have a valid PTR record. Both domains work correctly in practise. However one domain has the above issues. Both domains have Identical SOA records and NS records. Also of note is that the DNS has not had any changes carried out for a long time so the issue is not caching or TTL. Differences: There are some slight differences; 1) Domain Two (which works) has
localhost.domain.co.uk. 14400 A 127.0.0.1
There is no corresponding record for Domain One. 2) Domain One has a bunch of CNAME/TXT records by Stripe Payment Gateway for verifying the domain. These are not an issue as far as I can tell. 3) Domain One is only actually used for email, and the web domain is redirected (by CPanel / Domains / Redirects ) to a thirdparty for web hosting only. Questions: 1) How do I resolve this " Primary Name Server Not Listed At Parent " and "Local NS list does not match Parent NS list"? 2) Could the problem be at the domain name provider (run by the client so we don't have access)? 3) Could the problem be that the domain is auto-redirected, or that the domain does not have a localhost.domain DNS record as mentioned above?

Comments

3 comments

Date Votes
  • cPRex Jurassic Moderator
    Hey there! DNS is one area I sometimes struggle with over the Forums because it's hard to guess when using hypotheticals. For that problem, the most likely explanation is that something odd is happening at the registrar, but you wouldn't be able to see that unless you are the one that purchased the domain. I wouldn't expect the localhost record to be related to this at all. Can you have the client check the registrar settings?
    0
  • martin MHC
    Hey there! DNS is one area I sometimes struggle with over the Forums because it's hard to guess when using hypotheticals. For that problem, the most likely explanation is that something odd is happening at the registrar, but you wouldn't be able to see that unless you are the one that purchased the domain. I wouldn't expect the localhost record to be related to this at all. Can you have the client check the registrar settings?

    Hey Rex, thanks for getting back on this, I don't think it's strictly a WHM/CPanel issue, as you say, it seems to be the registrar is slightly off somehow. Using 3rd party tools I've found the registrar record is ns1.DomainOne.co.uk and ns2.DomainTwo.co.uk rather than the server NS1/2 ; eg NS1.serverDomain.co.uk . I believe this is the cause. I will do some testing with my working domain and see if it's as easy as redefining the NS points on the registrar. Cheers
    0
  • cPRex Jurassic Moderator
    Hopefully it's just that easy - let us know!
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post