DNS issues on Windows server 2008 network. Where to look?


We have just setup a new network with Windows 2008 server and about 10 PC's. The problem is many users complaining that the network is very slow.
For example one user today could not play an internet radio station, however when I logged into that workstation and changed the DNS settings to be 8888 suddenly it worked. Also when going to a website, often the initial web page takes a long while to come up or you get a page not found.

So something is going wrong with the DNS setup I assume.  But what can I check?

We just done a various simply installation of the network, created the domain using DCPROMO which would have installed DNS and set a forwarder in the DNS of the server. On the network the server and the workstations all have static IP addresses and each workstation has the DNS set to the server.

Any pointers on steps that should be taken to setup DNS when you first install a network?

Thanks in advance?
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.

Krzysztof PytkoSenior Active Directory EngineerCommented:
Run pathping command from a workstation and check where the latency occurs. It also shoudl show you at which step it's delayed ot stopped


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
afflik1923Author Commented:
OK I tried the pathping bit confused by the results but will research more. Even on my home computer seemed to take a long time to run. I assume that is normal. But more help about general setup would be good.
brwwigginsIT ManagerCommented:
Are you sure your DNS is configured to use forwarders? If so, try changing where it forwards to
afflik1923Author Commented:
Well that was one of our fears. It was forwarding to (google DNS) as mentioend in original posting but changed this now to be the IP's DNS (We were getting faster pings.

I think also I notice this.

When I set a workstation to have the IP address of the local server as DNS and run a flushdns it goes OK.
But if I put as the DNS in the workstation it seems to go faster.

What could be wrong?
afflik1923Author Commented:
Very belated respnse but the issue was unrelated to DNS in the end. Thanks
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

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.