Are you monitoring DNS via TCP or UDP?
Not sure that this will fix the problem, but Windows 2003 supports so called EDNS-0. This extension to DNS
allows requests larger than 484 bytes (512 byte packet) to be transported in UDP
DNS packets.
On the Windows 2003 machine which is sending out the DNS packets, you can run dnscmd /Config /EnableEDnsProbes 0. This will make sure that this machine uses TCP for its 484+ byte DNS queries. (You will need the Windows support tools for this - suptools.msi)
On the Windows 2003 machine which is sending out the DNS packets, you can run dnscmd /Config /EnableEDnsProbes 0. This will make sure that this machine uses TCP for its 484+ byte DNS queries. (You will need the Windows support tools for this - suptools.msi)
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Huey
Sent: Thursday, March 24, 2005 8:30 AM
To: [email protected]
Subject: [WhatsUp Forum] DNS monitoring under Windows 2003
I just upgraded the server I'm running WUG on from Windows 2000 to Windows 2003. I use WUG to monitor DNS on several servers. After the Win 2003 upgrade, I started to get a LOT of notifications about DNS being down on these servers. There doesn't actually seem to be any DNS problem with the servers -- it's just that WUG thinks there is. Has anyone else seen similar behaviour after a Windows 2003 upgrade? Thanks in advance for any help.
