I run a local webserver, and I have some fictitious domain names in my WinXP HOSTS file that point to 127.0.0.1 like: 127.0.0.1 verisignheadache.com Now, whenever I try to go to this domain, or any other domain pointing to 127.0.0.1, the request gets redirected to 64.94.110.11 (I'm assuming it has to do with the recent Verisign issue). I've tried suggestions of adding the entries: 127.0.0.1 64.94.110.11 and 127.0.0.1 sitefinder.verisign.com to my HOSTS file, but that doesn't seem to work. Any suggestions or ideas on why I can't have anything resolve to my local computer? Even if I try to force valid domains like microsoft.com to my local IP, they will keep resolving to the actual, correct IP, not the 127.0.0.1 that I gave it. However, if I use a different IP address, like 1.2.3.4, the HOSTS file will work and microsoft.com requests or whatever will go to that new IP address. It's almost like there's some hidden setting that is redirecting all 127.0.0.1 traffic to the new Verisign thingy. Thoughts? - Jonathan

whereever you are getting your dns from is what is correctly resolving the verisign address and not sending it to your ip loopback address. It would appear to me that dns is resolving then the hosts file. Good question to ask is who wins in a conflict between hosts and dns entries. DNS?

Instead of using 27.0.0.1 Localhost in the HOSTS file, use 0.0.0.0 Local. This avoids part of the loop back issue and is often faster. First make a backup copy of your current HOSTS file and try the following. At the start of the HOSTS file you should have an entry: 127.0.0.1 localhost after it add the entry: 0.0.0.0 local Then change all the following 127.0.0.1 left column entries to 0.0.0.0 and this might just solve part of your problems with HOSTS entries not working.