1

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:

;; ADDITIONAL SECTION:
ns1.hostlatch.com.  172800  IN  A   109.73.173.210
ns2.hostlatch.com.  172800  IN  A   109.73.173.211

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.

Tom
  • 11
  • 3

1 Answers1

0

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.

Tom
  • 11
  • 3