Quote:
Originally posted by desmocat Don't know what OS you are using, but sometimes when I get a lot of those, I open a command prompt and type:
ipconfig/flushdns
W2K caches the "page not found" hits as well, and it seems to want to go back to these before actually looking to see if it can get to the page.
Might work, might not, but it seems to help me out sometimes. |
My guess would be that these are sites using round robin DNS and one of the servers is out of sync. A page not found means that you reached the server but whatever you requested wasnt there. Could also be sites running dynamic IPs and it changed since you last visited and you are hitting someone else.
We see behavior like this at work when one server in a farm croaks or gets behind on replication. Gets hit and miss depending on which server you hit.
Could very well help his problem tho. Or it could just be old/dead links.