glue for nameservers

[halyfax]

My nameservers are on a .com domain and I get this warning for all my .ca domains that use my .com nameservers. Should I worry about this or should I get some .ca nameservers to help solve this issue?

"WARNING. The parent servers (I checked with ca04.cira.ca.) 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.#.#.##), 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."

[dammitjanet]

Peter

You could try to see if you can see any major discrepancies betwen DNS lookups using tracert, or extra hops caused by DNS referrals.

I dont personally know any tool that can give you a DNS lookup trace or timings, but then contrary to all things, i dont know everything. Someone else might know of a tool to query such.

[sdjl]

Have you edited your zone file templates to make the nameservers show as your own rather than dnsXX.gzo.com?

David

[halyfax]

I currently use my own nameservers, I haven't really had a problem but wondered because I did a report on dnsreport.com and this item failed for my .ca domains

[sdjl]

Does it just fail for your .ca domains only? Or are .com and other TLD's affected also?

David

[halyfax]

it only seems to fail for .ca's.....

.com's and .net's pass the glue test (although the .net failed the stealth test)

[sdjl]

mmm, i'm not sure what to suggest to get that working.
Most of my domains get a warning for the glue test on dnsreport.com

David

[danapier]

What does it mean NS in the same TLD?

I get this no Glue for nameservers for the two org sites that I provide DNS services for. TLD, Top Level Domain is what for the ORG guys? And wherre should these NS records go? Should I have a reference to .org in the Master Server? What would that look like? I cannot find anything about this in Cricket Liu's DNS Bind book. Anybody else solved this? Currently the ...org file has a reference to the NS Servers & they are ..com name servers.
When you check for timing the DNS for .org gets an F, but for the .com sites on the same DNS you get an A-. Whats up with that?

[Dan]

I have the same situation where the NS are .com and then some .org and .net domains. From what I was able to determine that is precisely the reason that it happens and I believe that it is due to CPanel's shortcomings. With my own domains there isn't any real difference in response time or loading time though and it has not caused any issues what so ever in the 3+ years I've seen this.

[sdjl]

i notice google.co.uk also shows no glue. So it's obviously nothing too worrying