DNS servers are not in the same TLD as domains - should I care?

[spaceman]

G'day.

We're a small Australian web hosting company, but we use a .com address for our name servers. The vast majority of the websites we host end in .au (for Australia).

This results in (at least) the following warning message when running a DNS Report for all of the .au sites we host:

WARN Glue at parent nameservers WARNING. The parent servers (I checked with dns1.telstra.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.

So I hear what they're saying - "you can speed up the connections slightly by having NS records that are in the same TLD as your domain." - but what do others think? Other than changing this line of the report from a WARN to a PASS, is it actually worth the minor hassle of changing my nameservers to be .au instead of .com? Will anyone actually notice? Have I made our hosting any more robust and/or easier to maintain if I do this?

Thx for your comments.

[brianoz]

It doesn't mean anything much ... if you had .com.au nameservers, the top-level .com.au servers would hand out the IP addresses of your nameservers when asked about the .com.au domain. This saves a DNS lookup to find their details and might make the very first visit to a webpage a little faster. Not a biggie ...

In terms of making anything easier to maintain - probably not. A .com.au domain is a little more manageable than a .com, that's about it I think!