Slow dns resolution

I have a server running SBS 2003 without the ISA server. There were no issues until this last weekend when I shut down the server to move it to a new server room. Upon rebooting the server at its new location, all internet is horribly slow both on the server and on all clients. The server was setup to resolve all dns (standard setup). Running a ping to an outside server takes about 15-20 seconds to resolve, and then once resolved it responds with very low latency. Similarly, when loading a large website, the dns takes forever to resolve, but after resolution, it loads very fast.

I tried switching the dns on the server and also the DHCP settings for the workstations to point towards the ISP's DNS servers. This resolved the resolutions issues for the outside web, but created a lot of issues on the internal network with name resolution.

Any forum I've searched so far about the issue seems to recommend simply using the ISP's dns servers for everything. I however, don't see this being a viable solution as I need the server to resolve the dns. Any help would be great!
b00meRrAsked:
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.

Shecky919Commented:
What is the resolution time like if you try to ping internally? I'd suspect bad cable to switch port for where the server is now.
0
powercramCommented:
Using your ISP's DNS servers exclusively is not a good solution - as you mentioned it creates problems with your MS domain.  In order for AD to work properly your clients need to use at least one internal AD/DNS server.

Try to ping the root DNS servers by IP address.  Are you having any trouble accessing them?
0
Darius GhassemCommented:
You should put your local DNS server's IP address in the server's TCP\IP. Also, you should only have your local DNS server IP listed in the client's TCP\IP settings. Check to make sure your Forwarders are up to date. You should never have an external IP address within the local network.


http://www.windowsnetworking.com/articles_tutorials/DNS_Conditional_Forwarding_in_Windows_Server_2003.html
0
b00meRrAuthor Commented:
The local DNS server's IP address is what I have in the server's TCP/IP. The server is a standalone server. It performs all DNS queries. The forwarders have been checked and are up to date. Pinging this server from the internal network is fast. However, the first ping to the server usually takes a little longer.
First pings are usually around 130ms, all subsiquent pings are 1ms.
As long as all dns pointers are pointed toward the SBS, the internal network runs fast. No problems. It's only when trying to resolve outgoing DNS queiries that it hangs.

Is there a way to recreate the DNS and possibly WINS databases? I suspect they may be corrupt.
0
Darius GhassemCommented:
Go into DNS clear the cache & Reload the zone.
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
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
SBS

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.