Unable to brose any .org websites

Our office has a pretty basic network setup. Comcast internet  service connected to a SonicWall router, which then has an Apple AirPort wireless router and and a linksys 8 port switch. We only have one SBS 2008 server acting as the domain controller and DNS server.

No changes have been made to any network components, but today we are unable to browse to any .org sites. .com, .net and other domains come up just fine at this point.

I am stumped as to what could be causing such a specific block, and am not sure what information would be pertinent to fully troubleshoot this.
Who is Participating?
I've had strange things like this happen when using root hints in windows dns servers. So much so, that I dont't set up root hints anymore. Try adding the Google DNS servers (, as Forwarders in the DNS server settings and delete the root hints.
How is DNS setup on the server? Is it using root hints or forwarding servers to outside DNS?
Go to something like MXTOOLBOX(.com) and query for the ip address of a .org domain.  Try to ping it ... try to do a nslookup from your network for the same domain.

If you are not getting the IP address, then it is a DNS issue (most likely with Comcast's servers) ... if you are getting an IP address, but are not able to ping it, then it may be a routing issue (unlikely that this will happen).

Also, Google gives out free DNS servers for people to use (I think it is and ... double check the IP addresses though).  Switch your DNS servers from Comcast to Google and see if you are able to get through (do the above mentioned tests with Google's servers too).

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

AidaPakITAuthor Commented:
Ok, making progress here.

If i set a computer on our network's DNS to, I can browse the web, but then lose the ability to get internal network DNS entries.

Our DNS server is using root hints, and has a series of a.root.servers.net for the FQDNs and has corresponding IP addresses for servers a through m (I did not set this up, and had pretty much left it alone until today)

So this seems to be a DNS issue with my server. I tried changing the DNS servers for the router to and and nothing changed. What settings might be causing this on my server though?
AidaPakITAuthor Commented:
That worked like a charm. thanks for the info!

Just out of curiosity, do you think there was something wrong with the root-server.net servers, or could something in my system have triggered this issue?
I would say something in your server. If the root hint servers have a problem, everyone does.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.