This question already has an answer here:

I have a client whose website has intermittent issues, which I believe are due to DNS lookup. When this happens and they do a ping, the host cannot be resolved. Therefore, I ran:

dig @a.gtld-servers.net autoquarterly.com

I get:

ns1.hostlatch.com.  172800  IN  A
ns2.hostlatch.com.  172800  IN  A

but these are not the correct IP addresses. If I do nslookup on the two nameservers, I get the correct IP addresses.

My question is where are these incorrect nameserver IP addresses coming from? I was under the impression these were glue records which are registered with the domain registrar. However, I noticed every domain I look up has the nameserver IP addresses in the ADDITIONAL section even though only domains which use a subdomain of their own domain name for their nameservers need glue records.

marked as duplicate by HBruijn, mdpc, MadHatter, Scott Pack, fuero Feb 18 '15 at 7:40

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • How could we possibly know? You didn't mention the domain. – gparent Feb 17 '15 at 18:59
  • In circumstances like this you should disclose the actual domain name if possible. – Michael Hampton Feb 17 '15 at 19:23
  • Okay, the domain is autoquarterly.com. Thanks for your help. – Tom Feb 17 '15 at 21:00
  • I checked the domain you gave and got similar results. You will want to change these entries yourself in your registrar's control panel, or if you really think this isn't your fault, you'll need to contact them to get them changed. – gparent Feb 17 '15 at 21:12
  • 1
    These are called glue records and they are maintained by your domain registrar. You should be able to change them using your domain registrar's admin site. – John Homer Feb 17 '15 at 21:20

There was an issue with the glue records for hostlatch.com. When I ran dig, the a.gtld-servers.net server found the nameserver names and then looked up their IP addresses in the glue records for hostlatch.com, not the glue records for autoquarterly.com or any other nameserver. It was the glue records set by the hostlatch.com registrar that needed to be changed.

Not the answer you're looking for? Browse other questions tagged or ask your own question.