Memory Leak

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The issue I am having is that every so often, and at random intervals, the
DNS service will eat up all memory on all our Domain Controllers and send all
sorts of monitors into alarm.
The systems have all the patches up to the end of Sept 2005. To resolve the
issue we have to stop DNS completely on all domain controllers and restart.
There is a zone transfer going on between our windows 2000 domain and our
2003 domain (no trusts involved), so not sure if that might be causing it.

We did find an MS support article that mentions the problem being something
to do with Glue records but we aren't using any glue zones plus the patch was
pre SP4

Any help would be appreciated.
 
Neil said:
The issue I am having is that every so often, and at random
intervals, the DNS service will eat up all memory on all our Domain
Controllers and send all sorts of monitors into alarm.
The systems have all the patches up to the end of Sept 2005. To
resolve the issue we have to stop DNS completely on all domain
controllers and restart. There is a zone transfer going on between
our windows 2000 domain and our 2003 domain (no trusts involved), so
not sure if that might be causing it.

We did find an MS support article that mentions the problem being
something to do with Glue records but we aren't using any glue zones
plus the patch was pre SP4
Click to expand...

This usually happens if there is a DNS loop happening. A DNS loop can be
caused by DNS servers forwarding to each other. It can also be caused by a
delegation with a missing glue record.
A glue record is needed for a DNS server to be able to resolve the NS
records in the delegation. In fact, all NS records need glue, make sure all
NS records have glue.
To check an NS record for glue double click the NS record in the zone or
delegation, see if it is resolved to an IP address and click the resolve
button to see if it can be resolved.
 
Back
Top