DNS on SBS 2008: cannot get to one web site

I have clients who cannot reach a certain domain's web site.  The users are on a domain (SBS 2008), and the server is the DNS server.

When I change the DNS of a workstation to something off site, it navigates fine.

There's a registry fix recommended involving MaxCacheTTL, but the recommended setting already exists.  As far as I know so far, it's just a single domain/URL that isn't working.  Is there a way to add this single site to the DNS server so that it works properly?  Or is there another recommended fix?

Thanks.
LVL 1
DaveWWWAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

becraigCommented:
Does this error occur when the users are using internal DNS servers ?

Try using nslookup problematic.domain.com  
See if you are able to resolve it using your dns servers.

If not I would just simply have the clients configured with a public dns as the secondary which should resolve this when the primary dns is unable to resolve the domain name.

You can add the zone to your DNS server and forward lookups to the internet but let's try to figure out if your dns server really cannot resolve the domain first and why.
0
VB ITSSpecialist ConsultantCommented:
Have you checked the DNS Forwarders on the DNS server? In Administrative Tools > open DNSright click on the server name > PropertiesForwarders tab

If you are using DNS Forwarders there's a possibility that the DNS server that you are using is having issues resolving the problematic domain. You can either notify them by contacting them directly or you can add in a working DNS server (something like OpenDNS) to the list as a workaround. I generally also reduce the number of seconds before the query times out to 1 second to boost the speed of DNS queries.

If this list is empty then it means the server is most likely using the Root Hint servers which don't always resolve domains out there. Best practice here would be to put in the DNS servers assigned to you by your ISP (you can get this info directly from your ISP or else you could log into your modem).
0
DaveWWWAuthor Commented:
becraig, I cannot Tracert the domain name.  It gives "Unable to resolve target system name..."  I can tracert the IP address, indicating a DNS issue I would presume.

When I use an OpenDNS server as the secondary DNS on the PC on the network/domain, it still does not resolve the domain name, strangely (even after Ipconfig /flushdns, etc.)

At ping.eu, the tracert is fine.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

becraigCommented:
Ok so that is your problem your DNS server is unable to resolve the DNS name, is this a domain you own ?

Or is it a general site on the internet ?

In any event I would just create a zone on my internal dns server and forward all lookup requests to the internet.

Simply create a forward lookup zone for www.domain.com and point that to your ISP dns server if the dns record is resolvable from their dns servers.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
VB ITSSpecialist ConsultantCommented:
DaveWWW2014-10-28 at 02:52:19ID: 40406590
When I use an OpenDNS server as the secondary DNS on the PC on the network/domain, it still does not resolve the domain name, strangely (even after Ipconfig /flushdns, etc.)
If you have the OpenDNS server set as the secondary DNS server, it will not handle the DNS requests for that machine unless your primary DNS becomes unavailable. Try setting the OpenDNS server as the primary then see if the domain is resolvable by pinging it in Command Prompt once you've changed over the orders of the DNS servers.
0
DaveWWWAuthor Commented:
Thanks very much - that solved my problem completely.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.

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.