DNS not working on 2003 server

I came in this morning and noticed our windows 2003 server isn't working correctly. All clients are windows XP Pro. When trying to ping server or workstations by name, it hangs about 10 seconds, then get ping reply. When connecting to server and other PC's via IP, there is no issue. I think maybe the server powered down improperly due to a power related issue. I tried typical things (rebooting server, restarting DNS, etc)

Please Help
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.

Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Is the W2003 server running the internal DNS service, too?
Is this a Domain ?

Have you tried te support tools

and DCDIAG ( if a Domian controller )

I hope this helps !

Henrik JohanssonSystems engineerCommented:
Ensure that the internal clients and server *only* use the internal DNS server for direct DNS resolving. Never use external/ISP DNS server for direct resolving, instead configure internal DNS server to use forwarders to forward unresolved queries to ISP's DNS server.
Let me get this straight:

You pinged by servername:

Ping servername

Ping is a multi-communications protocol diagnostic utility. If you pinged by servername, you are actually doing a netbios ping, not a DNS ping. This often deceives folks into troubleshooting DNS

Try this:

Ping Servername.fully.qualified.domain.name


NSlookup Servername.domain.name

If you have no problems with the fully qualified domain name, we might consider troubleshooting Netbios rather than DNS.
Henrik JohanssonSystems engineerCommented:
Ping servername without DNS suffix will try to append suffixes in DNS suffix search list and query DNS before using WINS/NetBIOS as DNS has higher priority than WINS/NetBIOS.

As it works sometimes, I'm pretty sure that the clients has been configured to use multiple DNS servers including some (external) server that isn't aware of the expected domain. This is a common mistake when trying to configure clients for redundancy of name resolution to be able to access internet resources.
Referring to an old consultant job I was out on for troubleshooting, they had configured their clients to only use external DNS servers (no internal DNS) and internal WINS server resulting in lack of performance when clients tried to access internal resources as they first queried internet DNS servers before failing over to use internal WINS.

As said, never use external DNS servers for direct resolving.

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
Windows Server 2003

From novice to tech pro — start learning today.