Is my DNS having a problem?

[JBruyet]

Hey all, I’ve had several of my users comment that they think the network is getting slower. I have thought that myself so I did a 30 minute local (no internet) network sniff with my Colasoft Capsa and found what I think are too many DNS errors. Here are the two highest error categories:

DNS server error (Server configuration errors) 693
DNS server slow response (Overloaded server) 419

I have two DNS servers (taking care of about 60 workstations) and the errors are coming from both of them. Server configuration for both servers is Windows Server 2003 SP2, Asus mobo w/Athlon 64x2 4600+, 1 gig RAM, 2 x 80 gig mirrored hard drives, 100Mb NIC. Event logs on both servers show an occasional, random error but nothing serious. I’ve tried using NSLOOKUP pointing to each server and everything I type in gets resolved. I downloaded DNSLint from the Microsoft web site and it doesn’t show any errors. I even made a quick MMC console for each server with the following counters: Pages/sec, % Disk Time, % Idle Time and % Processor Time and neither server is being “overloaded” that I can see. Are the DNS error numbers listed above “acceptable” or do I really have a DNS problem?

Thanks,

Joe B

 

[pagy]

Any errors reported when you run dcdiag and netdiag??

Paul
MCTS: Exchange 2007, Configuration
MCSA:2003
MCSE:2003
MCITP:Enterprise Administrator

If there are no stupid questions, then what kind of questions do stupid people ask? Do they get smart just in time to ask questions?
Scott Adams

 

[JBruyet]

Hi pagy,

DCDIAG on both servers comes back clean. The only error in NETDIAG is:

NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.

This error is on both servers but I didn't pay it much attention because the test passed. Any other ideas?

Thanks,

Joe B