Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm at work. Currently, we're having some fierce networking problems and every website I try to open throws an error similar to Firefox can't find the server at However, I can still browse StackOverflow and I am posting this, which proves that I'm not reading from cache.

How is this possible?

share|improve this question

migrated from Sep 15 '10 at 15:36

This question came from our site for computer enthusiasts and power users.

Sounds like a problem for SuperUser. – wheaties Sep 14 '10 at 20:54
Sounds like DNS issues. – Stefan Kendall Sep 14 '10 at 20:56
Point your DNS at and and see what happens. – Stefan Kendall Sep 14 '10 at 20:57
So now you've migrated the question from the one site he can still reach to one he can't. I understand the motivation, but realize that you didn't do him any favors. – Mark Ransom Sep 14 '10 at 21:00

your network is experiencing DNS outage. SO name is still in the local DNS resolver cache.

share|improve this answer
Wow, what does it say about SO that he has SO in his DNS resolver cache, but not google???? – BillN Sep 15 '10 at 20:05

Sounds like a DNS issue. Point your DNS at and and see what happens.

share|improve this answer

For this specific issue it sounds like @Franci Penov and @iftrue are right - you're having DNS issues.

On a more general level you should make sure you have some sort of connectivity in case your primary network goes down. This can be a separate connection (DSL + cable or dialup), a cell phone with a data plan and tethering, or the local coffee shop.

share|improve this answer

dig is your friend here for analysing DNS issues. If you're a Windows man like me, you can get dig for Windows from Nicholas Fong's site. (site also has basic user guide on it) - if you can't resolve it, the server's IP is for your hosts file!

Find out the IP address of your primary DNS server then run

dig @ip.of.dns.server

If that yields something with

com.                    900     IN      SOA

(or similar) in the results, then your DNS server's poorly. If you get a list of results in the ANSWER section including, and (for example) then your DNS resolver is working and your own PC is not.

As others have said, try Google's DNS servers. Alternatively, try OpenDNS' servers: and Best of luck...

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.