if you tried to resolve it, for some reason it resolves to 127.0.0.1, but in my exploration of their DNS, I found a IP address and it works!

http://216.142.16.242

It's a really great site.

Uhhh... What are you talking about.

Sysinternals.com has never resolved to the loopback for me ever. I can ping by name fine, type it in the address bar and it goes there, and using your DNS crawler I found it no problem.

Try for yourself: www.sysinternals.com

Link to SR\'s dns crwaler

You got me kinda confused here SR.

This is extremely odd. Me and rage both had this problem of not being able to resolve it. The link rage provided works for no problem. Infinite's link does not. My linux box resolves it perfectly with ping, nslookup, in the browser everything. My XP machine resolves it locally. So what I think is that some software installed on my machine changed something in the hosts file and after looking, I see that I was right. Now, I know that kazza light uses a modified hosts file to block ads. I think thats what it might be from. even though now that im looking at this file a LOT of security sites have been switched to resolve locally...

[18:37] * Looking up www.sysinternals.com
-
*** ---[ DNS! ]------------------------------------------
*** Found: 1 addresses
*** Nick:
*** DNS: www.sysinternals.com
*** Address: www.sysinternals.com
*** IP: 216.142.16.242
*** ------------------------------------------------------------
-
[18:38] * Resolved www.sysinternals.com to 216.142.16.242

It works fine for me too..

----------------------------------------

C:\>ping www.sysinternals.com

Pinging sysinternals.com [216.142.16.242] with 32 bytes of data:

Reply from 216.142.16.242: bytes=32 time=906ms TTL=111
Reply from 216.142.16.242: bytes=32 time=859ms TTL=111
Reply from 216.142.16.242: bytes=32 time=859ms TTL=111
Reply from 216.142.16.242: bytes=32 time=890ms TTL=111

Ping statistics for 216.142.16.242:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 859ms, Maximum = 906ms, Average = 878ms

C:\>

----------------------------------------------

Could be that your XP box has it's hosts file setting that domain to 127.0.0.1. Some ad-blocking software does that to a list of known adsites (doubleclick.net, etc.) or it coulda happened by accident.

For both of you to have the same problem, kinda odd tho...