Help - Search - Members - Calendar
Full Version: Glue Problem
The Planet Forums > System Administration > DNS Hosting
JDC
I set up my main site on my Windows 2003 server with Plesk 7.5 and all is well. I have begun to add some other client sites to the server. When I check the client domain at dnsreport.com, I see that I'm getting a warning under "Glue at parent nameservers" with the following explanation:

QUOTE
WARNING. The parent servers (I checked with TLD1.ULTRADNS.NET.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.


The sites do work fine, but I'm neurotic enough to want to remove as many warnings as possible from the report. Any ideas how I can go about fixing this issue?

Thanks in advance!
eddy2099
Was the site just recently added to your DNS Servers ? If so, give it a while for the DNS Zone servers to get propagated fully and the errors would automagically go away.

This happens when you add a domain to your dns and the domain came from another host. At that time, not all information of all the DNS Zone servers have been sychronized with the new information, some might point to the old while the others pointing to the new. Thus the error.

Check the DNS Report in 48 hours.
S3
I have .com nameservers, and I get that warning on .org and .us domains I host, but not on .com or .net. I've never gotten too concerned about it.
cprompt
This is down to the root servers for the TLD - .com and .net provide glue, while .co.uk and others don't.

All it means is that when the root servers provide the parent name servers (eg TLD1.ULTRADNS.NET) they either provide the IP as part of the answer or they don't, in which case the client needs to look up the IP of the parent server as a separate request.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.