We have a DNS server at work that maps
<developername>.zende.sk to each developer's computer so we can see one another's work. These paths are not routable from the WAN. On OSX and on virtualized Windows (which I presume uses the underlying OSX's DNS lookups), I can go to
http://me.zende.sk, but this fails on a Windows XP machine.
When I run
nslookup me.zende.sk from the Windows machine, I get
Server: someresolver.com Address: 220.127.116.11 Non-authoritative answer: Name: something.zende.sk Address: 18.104.22.168 Aliases: me.zende.sk.zende.sk
I tried going to
http://me.zende.sk.zende.sk and it worked like a charm. Why?
I've gone into my networking settings in Windows and fiddled with the "Append primary and connection specific DNS suffxes," "Append parent suffixes of the primary DNS suffix," and "Append these DNS suffixes (in order)" settings, all to no avail.