S
Steve
Your gonna love this problem (mistake/bug/slip up):
If you create a file:
"c:\windows\help\hosts"
lets call this one (A)
and create a few entries in there just like you would in the normal,
"c:\windows\system32\drivers\etc\hosts"
call this one (B)
such as:
111.111.111.111 test.com
It will be used just like the (B) file - which it certainly shouldn't.
I have seen a lot of people asking about cahced DNS entries that just
don't seem to go away with the:
"ipconfig /flushdns"
command, and this fixed the same problem I had. Somehow (A) was
created by something and had references to all of googles sites
resolving to a different IP. I found it after doing a "ping
google.com" and had it resolve even after disconnecting from the
network, from there I just did a text search with ultraedit on my HD
for anyfile containing that IP.
Cheers
If you create a file:
"c:\windows\help\hosts"
lets call this one (A)
and create a few entries in there just like you would in the normal,
"c:\windows\system32\drivers\etc\hosts"
call this one (B)
such as:
111.111.111.111 test.com
It will be used just like the (B) file - which it certainly shouldn't.
I have seen a lot of people asking about cahced DNS entries that just
don't seem to go away with the:
"ipconfig /flushdns"
command, and this fixed the same problem I had. Somehow (A) was
created by something and had references to all of googles sites
resolving to a different IP. I found it after doing a "ping
google.com" and had it resolve even after disconnecting from the
network, from there I just did a text search with ultraedit on my HD
for anyfile containing that IP.
Cheers