Hi All!
Getting a similar issue to one experienced in - http://social.technet.microsoft.com/Forums/en/winserverNIS/thread/c06c9c51-002a-4ca8-aea7-c89e5a7d17ad
We currently have two AD 2003 SP2 DNS servers in different locations, both reported the same error 5 minutes apart which obviously caused all DNS lookups to fail. In order to restore services as quickly as possible we rebooted both servers a few minutes apart to resolve the issues, which means we didn't see the actual memory usage of DNS or run the command DNSCMD /STATISTICS
Looking at the posts we haven't applied any patches to the servers in the last 2 months. We also don't have hotfix 941672 or the fix 975830 installed. Looking at DNS we are using a newer version than described in the articles anyway - 5.2.3790.4957 (srv03_sp2_gdr.120130-0234) (30-Jan-2012). Which means we have applied KB2647170.
After a reboot everything seems normal, memory allocated to DNS is under the 60MB mark. However, we are seeing high "InUse" values when runningDNSCMD /STATISTICS -
Tagged Allocations:
None
Alloc = 3
Free = 1
InUse = 2
Mem = 180
UDP Packet
Alloc = 9106
Free = 0
InUse = 9106
Mem = 24768320
TCP Packet
Alloc = 8443
Free = 6394
InUse = 2049
Mem = 36414828
The above post mentions any "InUse" values over a few hundred can indicate a memory leak which we are seeing. Does the fix advised in the post still apply "SetEnableDuplicateQuerySuppression to zero" ? Or is there another hotfix available to resolve this?
Thanks in advance!