[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 552
  • Last Modified:

How do I fix nameserver glue error using BIND

I recently cahnged ISPs at one of our locations.  Our secondary nameserver is there and I am not able to get the root servers to see the change.  I ran a dnsreport and saw the following error.

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:

Parent server (f.gtld-servers.net) says A record is 12.178.70.56, but
authoritative DNS server (64.17.232.76) says it is 173.13.126.132

We are our own DNS provider and I believe I have changed all the records that need to be changed, but the ns2 change will not seem to propagate.    Any thoughts?
0
DanRaposo
Asked:
DanRaposo
  • 2
  • 2
1 Solution
 
Chris DentPowerShell DeveloperCommented:

If the parent is incorrect you will need to change it with your domain registrar, you won't be able to change glue on the parent directly.

Chris
0
 
DanRaposoAuthor Commented:
Chris,

Thanks for the quick reply.  I didn't think  I had to change anything at the registrar because the only info I gave them was the hostnames of the name servers, since we run our our DNS zones I changed the ip address on our name servers and thought it would spread.   I have logged a request with go daddy already because I cannot find any reference on the site to update it myself.
0
 
Chris DentPowerShell DeveloperCommented:

They take the host names, resolve them to IPs, then use the result as glue. If the name hadn't resolved they'd have asked you for an IP.

Generally there's no automatic update of glue at the parent. Hopefully they'll be able to change it for you pretty quickly.

Chris
0
 
wdurrettCommented:
Dan,

Chris is correct.  If you log into your register, you shoddily be able to see your nameservers and IP addresses.  You need to update that record with them.

For instance, say this was ns1.domian.com.  At your register (Dotster, GoDaddy, Network Solutions), they keep a record of nameserer IPs.  Log in and make sure ns1.domain.com at your register points to the new IP address.

All major registrars have a web interface where you can update these records.
0
 
DanRaposoAuthor Commented:
Finally found where it was listed at the domain registrar.  Thanks for your help.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now