North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Fixing .com DNS glue records - who to contact?

  • From: william(at)elan.net
  • Date: Tue Aug 16 17:39:29 2005 
On Tue, 16 Aug 2005, Matthew Elvey wrote:
A glue record for a .com domain (nextbus.com) is wrong, and I'm running into a brick wall trying to get it fixed.
Do I need to switch to a more clueful registrar than GoDaddy**? Contact Network Solutions?
Have I screwed up the domain's bind config? Everything looks right when I _dig_ around the authoritative NS*..
I futzed with the record (deleted and re-added ns.nextbus.com as an authoritative NS (nameserver(s))), and the glue became correct for several days (dnsreport.com even reported all was well) AND THEN WENT BACK TO BEING BROKEN AGAIN.
$ dig nextbus.com @ns.nextbus.com
;; AUTHORITY SECTION:
nextbus.com. 14400 IN NS b.auth-ns.sonic.net.
nextbus.com. 14400 IN NS c.auth-ns.sonic.net.
nextbus.com. 14400 IN NS ns.nextbus.com.
nextbus.com. 14400 IN NS a.auth-ns.sonic.net.

;; ADDITIONAL SECTION:
a.auth-ns.sonic.net. 38814 IN A 209.204.159.20
b.auth-ns.sonic.net. 38814 IN A 64.142.88.72
c.auth-ns.sonic.net. 38814 IN A 69.9.186.104
ns.nextbus.com. 14400 IN A 64.142.39.200
^
from your dns server

$ dig +norecurse ns.nextbus.com @a.gtld-servers.net

;; ANSWER SECTION:
ns.nextbus.com. 172800 IN A 64.164.28.194

;; AUTHORITY SECTION:
nextbus.com. 172800 IN NS a.auth-ns.sonic.net.
nextbus.com. 172800 IN NS b.auth-ns.sonic.net.
nextbus.com. 172800 IN NS c.auth-ns.sonic.net.
nextbus.com. 172800 IN NS ns.nextbus.com.

;; ADDITIONAL SECTION:
a.auth-ns.sonic.net. 172800 IN A 209.204.159.20
b.auth-ns.sonic.net. 172800 IN A 64.142.88.72
c.auth-ns.sonic.net. 172800 IN A 69.9.186.104
ns.nextbus.com. 172800 IN A 64.164.28.194
^
from .COM glue record

$ dig +nssearch nextbus.com @a.gtld-servers.net
SOA ns.nextbus.com. noc.nextbus.com. 2005072902 28800 3600 604800 86400 from server a.auth-ns.sonic.net in 43 ms.
SOA ns.nextbus.com. noc.nextbus.com. 2005072902 28800 3600 604800 86400 from server b.auth-ns.sonic.net in 25 ms.
SOA ns.nextbus.com. noc.nextbus.com. 2005072902 28800 3600 604800 86400 from server ns.nextbus.com in 24 ms.
SOA ns.nextbus.com. noc.nextbus.com. 2005072902 28800 3600 604800 86400 from server c.auth-ns.sonic.net in 85 ms.

So the answer is that you need to make sure your own dns server "A"
record for "ns.nextbus.com" matches glue record entered with registrar.
As far as what is going to be used by global dns, it would be glue
record that you set with registrar (ok - its supposed to, but its
not always true depending how caching dns server is written).

BTW - when doing check make certain to use "+norecurse"

I have tested your site and everything is resolving properly. This error message you are getting is not on our end.
If the record you wanted for glue is 64.142.39.200 and godaddy did not
fix it, then I suggest you find more cluefull registrar support person.
Thank you for contacting customer support. I have looked into this situation and found that the domain name in question is not hosted with us. This being the case you may wish to speak with your hosting provider regarding the "glue" situation.
The above is a red flag that the godaddy's "customer service representative"
has no idea what "glue" means. Escalate to the real tech support.

--
William Leibzon
Elan Networks
[email protected]