Does anyone bother with nameservers for each TLD to get "glue"

[Jeff]

WARNING. The parent servers (I checked with tld5.ultradns.info.) 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.
So how many people bother having ns1.domain.com, ns1.domain.org, ns1.domain.net, ns1.domain.us, ns1.domain.info, etc. to "speed up the connections slightly" by having glue at the parent servers?

[Laurie-Resell1]

So how many people bother having ns1.domain.com, ns1.domain.org, ns1.domain.net, ns1.domain.us, ns1.domain.info, etc. to "speed up the connections slightly" by having glue at the parent servers?


If you will email your specific issue with the DNS we can help you add the nameservers to all the foreign (TLD) registries through the RWI, to support@resellone.net. Please include your account username in any correspondence.