Mismatched glue

Tauvo

Tauvo

Verified User
Joined
Jul 29, 2005
Messages
22
Location
Rochester, NY
Hello everyone,

I have a question that I have been trying very hard to correct on our end by doing as much as I can first before I posted here. I have done all of the "googling" and forum searching that I can so far and not finding any solution that makes sense to me. I imagine that at some point I will find our error and it will just jump right out at me and say HERE I AM! But until that time can someone please point me in the right direction? Here is what I see from the DNS Reports website.

FAIL

Mismatched glue 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:
ns2.dlb1.net.:
Parent server (b.gtld-servers.net) says A record is 66.193.26.35, but
authoritative DNS server (66.193.26.34) says it is 66.193.26.34

ns2.dlb1.net.:
Parent server (b.gtld-servers.net) says A record is 66.193.26.35, but
authoritative DNS server (66.193.26.35) says it is 66.193.26.34

and here is the info that I can provide for this server.

eth0 is 66.193.26.34
eth1 is 66.193.26.35

Here is the info from /etc/sysconfig/network-scripts

DEVICE=eth0
BOOTPROTO=none
BROADCAST=66.193.26.63
HWADDR=00:10:DC:33:A7:AB
IPADDR=66.193.26.34
NETMASK=255.255.255.224
NETWORK=66.193.26.32
ONBOOT=yes
TYPE=Ethernet
GATEWAY=66.193.26.33

DEVICE=eth1
BOOTPROTO=none
BROADCAST=66.193.26.63
IPADDR=66.193.26.35
NETMASK=255.255.255.224
NETWORK=66.193.26.32
ONBOOT=yes
TYPE=Ethernet
GATEWAY=66.193.26.33
 
This means that your registrar, NAMES4EVER, has your name servers listed as:

ns1.dlb1.net 66.193.26.34
ns2.dlb1.net 66.193.26.35

However, the nameservers themselves (i.e., bind running on your machine) are reporting the A record of ns2.dlb1.net to be

ns2.dlb1.net 66.193.26.34

which doesn't match what the registrar says it should be.

So, go into your admin panel -> DNS Admin -> dlb1.net, delete the ns2 A record and add a new A record for ns2 pointing at 66.193.26.35.
 
That fixed the problem. I knew it would be an easy fix but I can see that I was looking in all the wrong areas. Thank you for the fast reply and excellent advice.
 
ballyn said:
This means that your registrar, NAMES4EVER, has your name servers listed as:

ns1.dlb1.net 66.193.26.34
ns2.dlb1.net 66.193.26.35

However, the nameservers themselves (i.e., bind running on your machine) are reporting the A record of ns2.dlb1.net to be

ns2.dlb1.net 66.193.26.34

which doesn't match what the registrar says it should be.

So, go into your admin panel -> DNS Admin -> dlb1.net, delete the ns2 A record and add a new A record for ns2 pointing at 66.193.26.35.
Click to expand...

OK .. I have a question

I changed the IPs that my nameservers point to the other day, as I did not like the ns record pointing at a website that is private ...

now I have mismatched glue on over 300 domains ... how do I correct this without going and entering new A records for 300+ domains one at a time? :eek:
 
Code: 
cd /var/named
perl -pi -e 's/[b]old.IP[/b]/[b]new.IP[/b]/' *.db
 
Oke, I've got a question regarding this matter, using dnsreport.com, it shows these settings:

Your NS records at the parent servers are:

ns1.ispd.nl. [81.171.86.50] [TTL=7200] [NL]
ns2.ispd.nl. [81.171.86.51] [TTL=7200] [NL]
[These were obtained from b.nic.fr]
Click to expand...

But ns2.ispd.nl should have IP address 81.171.86.111, for some reason b.nic.fr is still showing my old ns2 IP address and therefor I get this message:

ns2.ispd.nl.:
Parent server (b.nic.fr) says A record is 81.171.86.51, but
authoritative DNS server (81.171.86.50) says it is 81.171.86.111
ns2.ispd.nl.:
Parent server (b.nic.fr) says A record is 81.171.86.51, but
authoritative DNS server (81.171.86.51) says it is 81.171.86.111
Click to expand...

How do I solve this issue other than changing ns2 back to the old IP address? I cannot change it back to the old IP because then my redundancy is gone (yeah I know, they're on the same subnet, but on different machines)

Thanks in advance,

Regards, Jeroen.
 
Did this work itself out? Generally this may occur during the period the changes haven't completely propagated.

Jeff
 
Hi Jeff,

No it hasn't worked itself out and I have no idea how to fix this issue.

Regards, Jeroen.
 
Have you posted the link to the report? I didn't see it, but I could have missed it.

Jeff
 
Got it:
ns2.ispd.nl.:
Parent server (ns-ext.isc.org) says A record is 81.171.86.51, but
authoritative DNS server (81.171.86.51) says it is 81.171.86.111
ns2.ispd.nl.:
Parent server (ns-ext.isc.org) says A record is 81.171.86.51, but
authoritative DNS server (81.171.86.50) says it is 81.171.86.111
Click to expand...

The nameservers for ns2.ispd.nl says that the A record for ns2.ispd.nl resolves to 81.171.86.111, but the registrar (where presumably you registered your nameserver, says the A record for ns2.ispd.nl resolves to 81.171.86.51.

The only way to resolve this is with your domain registrar. First try registering your nameservers (again, if you've already done so) at your registrar. Second make sure you use the same IP# you've just registered in your nameserver's zone file.

Jeff
 
You must log in or register to reply here.
Back
Top