Quote:
Originally Posted by karbomusic
Then he couldn't get here or check via browser. However, if it were the DNS cache then ipconfig /flushdns is the command to force it to do a new DNS lookup. I suppose it's possible he could have the wrong DNS servers, but that would be really, really odd with basic DHCP.
|
I've seen more than a few times where DNS is only partly hosed, and I could get to *almost* all sites, but not all of them. A release/renew fixed it almost every time.
My gut feeling is that some server in the sky, or possibly a whole farm of them hosted by AWS, become unreachable due to either some kind of memory corruption, or possibly a hijack from some web page.
When I've seen it, I can type something like cnn.com into my browser and it goes there, but then some other site will time out and give me an error. Doing a release/renew almost always corrects the problem, but at least once or twice I've had to dump my modem's connection and let it get it's DNS reestablished.
Here's a link to a possible reason a /release /renew would work.
https://serverfault.com/questions/48...s-client-issue