Win2k3 SBS DNS issues

Had a problem that started Friday- For some reason, some DNS requesta do not seem to be resolving. I am using MS DNS server on a sbs, all the clients point to the server as the DNS server. I have2 forwarders to 2 different ISP dns servers enabled. When I do an nslookup, i get a response. from internet exploiter, i can go to sites like google and yahoo, but not microsoft.com, msn.com,and mapquest.
i have scavenged all stale records, cleared my cache,andrestarted the server. if i change a client to not use the server as its dns, it works fine.

dunno if it makes a difference, but ialso have a particular client that has incredibly slow login times, too.
DoctorlloydAsked:
Who is Participating?
 
visioneerConnect With a Mentor Commented:
How about you turn off the forwarders and let the server do recursive lookups?

Also, go to the Properties of the DNS server, Monitoring tab, and run the local and recursive query tests, see if they both pass.
0
 
DoctorlloydAuthor Commented:
Both of the tests pass, I will turn off forwarders.
0
 
DoctorlloydAuthor Commented:
Ok- i turnedoff forwarders,andnow i fail on recursive tests. EEK!
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
visioneerCommented:
Try turning forwarders back on, and forward to different DNS servers.  
0
 
oBdACommented:
On the clients (pointing to your internal DNS server), enter
nslookup microsoft.com,
then
nslookup microsoft.com <IP-address of your ISP's DNS>
and compare the results.
If they're different, on your DNS server, run
ipconfig /flushdns
and immediately afterwards
ipconfig /displaydns >dns.txt
This will give you a text file "dns.txt", which you can open in notepad. Look if there are entries for the troublesome names present (shouldn't be).
If they are there, your hosts file has been manipulated. Check if the "DataBasePath" value at HKLM\System\CurrentControlSet\Services\tcpip\Parameters still points to %SystemRoot%\System32\drivers\etc; if not, change the value back. Then open the "hosts" (no extension) file in this directory and make sure there are no rogue entries there. Then, obviously, check your system for spyware and viruses; there are tons of links for that available at EE.
Then there's the standard stuff:

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?kbid=291382

HOW TO: Set Up the Domain Name System for Active Directory in Windows Server 2003
http://support.microsoft.com/?kbid=816584

HOW TO: Configure DNS for Internet Access in Windows Server 2003
http://support.microsoft.com/?kbid=323380

HOW TO: Troubleshoot DNS Name Resolution on the Internet in Windows Server 2003
http://support.microsoft.com/?kbid=816567
0
 
DoctorlloydAuthor Commented:
It was the forwarders- it took a bit for the thing to resolve itself, then finally it did. Not surer what caused it to stop working... I just accept it sometimes, then forget exactaly how important DNS is to win2kx these days.  It even wreaks havoc with SQL servers, too.
Thanks all.
0
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.