Re: Why does this hostname resolve?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Aries1.upscalehost.com is an authoritative nameserver itself, and actually
still hosts the upscalehost.com domain even though the NS records on GTLD
don't point to it (aries2 also). The GTLD servers are authoritative for IP
addresses of lower level authoritative nameservers, so this explains why you
are getting the A record. Try querying them for dns1.upscalehost.com and
you'll get the same kind of result. It also points out a problem with the
way the system works, because obviously the GTLD servers are trusting aries1
to provide its IP address over dns1 and dns2. This might just be a caching
issue, but I'm not sure about that.

--
Greg Lindsay [MSFT]

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

"RC" <wishbone0@xxxxxxxxxxx> wrote in message
news:1166459835.274888.224970@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I don't understand why the hostname aries1.upscalehost.com resolves.

If I query the authoritative servers (dns1.upscalehost.com and
dns2.upscalehost.com) directly, they do not resolve the hostname to an
IP. But if I query one of the gtld-servers.net servers (expecting to
only get a response containing NS records), I end up getting an A
record response.

I can't figure out why the GTLD servers are responding with a
non-authoritative A record (aren't they supposed to be non-recursive?)

-RC



.