Fixing .com DNS glue records - who to contact?

Tue Aug 16 21:19:19 UTC 2005

On Tue, 2005-08-16 at 14:10 -0700, 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.

The problem is that the A and PTR records for your domain servers don't
match up. See the "Mismatched glue" section of your dnsreport.  

I've got the same issue with some domains hosted over at Register.com's
GPN (Global Partner Network) division.  GPN outsources DNS to eNom
(which is an excellent thing), but the default GPN DNS settings use
dnsXX.gpn.register.com which has a PTR to dns1.name-services.com.  I
*think* that this is OK per RFC, would really like to hear some expert
opinions on this however.

-Jim P.

> 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.
> 
> http://www.dnsreport.com/tools/dnsreport.ch?domain=nextbus.com
> currently says: 
> ns.nextbus.com.:
>    Parent server (f.gtld-servers.net) says A record is 64.164.28.194, but
>    authoritative DNS server (209.204.159.20) says it is 64.142.39.200
> ns.nextbus.com.:
>    Parent server (f.gtld-servers.net) says A record is 64.164.28.194, but
>    authoritative DNS server (64.142.88.72) says it is 64.142.39.200
> ns.nextbus.com.:
>    Parent server (f.gtld-servers.net) says A record is 64.164.28.194, but
>    authoritative DNS server (69.9.186.104) says it is 64.142.39.200
> 
> 
> 
> ALSO: Since 3 of the 4 NS don't have the wrong glue, and 4 of the 4 NS 
> are answering appropriately, and there's no NS at the IP indicated by 
> the wrong glue, this problem shouldn't have any user-visible impact, 
> right?  I think there are many ISPs (I've found Earthlink and SBC to be 
> guilty of this in the past) who have broken their resolver 
> configurations so that they sometimes don't work if one, but not all of 
> a domain's NS don't answer.  Anyway, I'm getting complaints (from a 
> gov't agency) of mail bouncing with '450 Client host rejected: cannot 
> find your hostname' errors. 
> 
> TIA.  This is my first post here; please be gentle.
> 
> Oh, and if I do need a new registrar, I'm taking suggestions here or here:
> http://wiki.fastmail.fm/index.php/GoodRegistrarSearch
> 
> 
> *dig nextbus.com MX
>  dig nextbus.com MX @ns.nextbus.com.
>  dig nextbus.com MX @a.auth-ns.sonic.net.
>  dig nextbus.com MX @b.auth-ns.sonic.net.
>  dig nextbus.com MX @c.auth-ns.sonic.net.
> 
> **edited to conform to normal attribution.  WARNING: C&C.
> Subject: [Fwd: Please fix this Mismatched glue problem for domain 
> nextbus.com [Incident: 050729-000962]]
> Me:
>  > Go Daddy:
>  >> Me:
> >>> Please fix this Mismatched glue problem for domain nextbus.com:
> >>>
> >>> ERROR: Your nameservers report glue that is different from what the
> >>> parent servers report. This will cause DNS servers to get confused; 
> >>> some
> >>> may go to the IP provided by the parent servers, while others may 
> >>> get to
> >>> the ones provided by your authoritative DNS servers. Problem 
> >>> record(s) are:
> >>>
> >>> ns.nextbus.com.:
> >>> Parent server (m.gtld-servers.net) says A record is 64.164.28.194, but
> >>> authoritative DNS server (208.201.224.11) says it is 64.142.39.200
> >>> ns.nextbus.com.:
> >>> Parent server (m.gtld-servers.net) says A record is 64.164.28.194, but
> >>> authoritative DNS server (208.201.224.33) says it is 64.142.39.200
> >>>
> >>> The glue in the parent servers is wrong.
> >>
> >> Thank you for contacting customer support.
> >>
> >> I have tested your site and everything is resolving properly. This 
> >> error message you are getting is not on our end.
> >>
> >> Please let us know if we can help you in any other way.
> >>
> >> <Advertisement for GoDaddy services removed> 
> >>
> >> Sincerely,
> >>
> >> Beth P.
> >> GoDaddy.com
> >> Customer Service Representative
> >
> > Please have this issue reviewed by someone technical - someone who knows
> > what DNS glue is, so they can understand the error in my initial email.
> > See
> > http://www.menandmice.com/online_docs_and_faq/glossary/glossarytoc.htm?glue.record.htm 
> >
> > or http://www.centralnic.com/support/glossary
> >
> > http://www.dnsreport.com/tools/dnsreport.ch?domain=nextbus.com
> > shows quite clearly IN RED that there is something seriously wrong.
> > The problem exists. It is NOT my imagination.
> > Just because you're able to bring up www.nextbus.com does NOT mean
> > there's nothing wrong.
> 
> 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.
> 
> Please let us know if we can help you in any other way.
> 
> <Advertisement for GoDaddy services removed>
> <https://www.godaddy.com/gdshop/hosting/landing.asp?isc=webxpf>
> Sincerely,
> 
> Kade P.
> 
> --
> Matthew
> http://wiki.fastmail.fm/index.php/MrElvey
> 
> 
> 