windows 2003 dns high CPU utlization

  • Thread starter Thread starter Blake
  • Start date Start date
B

Blake

My DNS servers (Win2k3 upgraded over Win2k) will run flawlessly for several
days/weeks. The CPU utlitization will slowly climb until they get to a
point where they peg my processor. This happens on both boxes.

Is there a memory leak with the newest version of DNS server? I have seen
reports of this behavior in my web searching but no solutions.

Thanks

Blake
 
In
Blake said:
My DNS servers (Win2k3 upgraded over Win2k) will run
flawlessly for several days/weeks. The CPU utlitization
will slowly climb until they get to a point where they
peg my processor. This happens on both boxes.

Is there a memory leak with the newest version of DNS
server? I have seen reports of this behavior in my web
searching but no solutions.
Click to expand...

Both boxes?
Any chance the DNS on these two boxes are forwarding to each other?
If they are, then this will cause a DNS loop which results in your behavior.
Do not forward two DNS servers to each other, always forward out to another
DNS server that does not forward back in.
 
Not a bad thought Kevin, but these boxes aren't forwarded to each other.

These 2 boxes are our 'public' DNS servers, and neither is forwarded. (our
internal DNS servers ARE forwarded to these 2)

I wasn't having any problems until these machines were upgraded to Windows
2003. They ran with this DNS config for 3 years on Win2K.

Thanks
Blake
 
Hi Blake

I've seen a number of code revisions to dns.exe for Windows Server 2003 in
the form of hotfixes but none of them have been to specifically address the
issue you're describing. It may be the case that in order to track this
down, you'd need to go through a reasonable degree of debugging with PSS.

You might be experiencing this:

830381 Server Responsiveness Degrades and Queries Time Out When You Run the
DNS
http://support.microsoft.com/?id=830381

HTH
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.
 
The memory usage of DNS.EXE also starts climbing and gets upwards of 67
Megabytes. I would understand if there was some memory utilization for the
DNS cache, but this seems excessive. DNS is not normally considered a real
intensive service.

I have considered re-loading one of these machines - do a clean install of
Win2k3 instead of an upgrade. I have also considered simply waiting for SP1
to be released. Not sure what I should do.

Thanks

Blake

Mark Renoden said:
Hi Blake

I've seen a number of code revisions to dns.exe for Windows Server 2003 in
the form of hotfixes but none of them have been to specifically address
the issue you're describing. It may be the case that in order to track
this down, you'd need to go through a reasonable degree of debugging with
PSS.

You might be experiencing this:

830381 Server Responsiveness Degrades and Queries Time Out When You Run
the DNS
http://support.microsoft.com/?id=830381

HTH
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no
rights.

Blake said:
Not a bad thought Kevin, but these boxes aren't forwarded to each other.

These 2 boxes are our 'public' DNS servers, and neither is forwarded.
(our internal DNS servers ARE forwarded to these 2)

I wasn't having any problems until these machines were upgraded to
Windows 2003. They ran with this DNS config for 3 years on Win2K.

Thanks
Blake
Click to expand...
Click to expand...
 
Hi Blake

If you're considering a rebuild of a box anyway, it can't hurt to try the
latest dns.exe binary to see if the issue you've got has been fixed. While
not the approach you'd normally take with a production server, the fact that
you're considering a clean install lends itself to this test.

Not all code changes are documented and hotfix releases include all prior
code changes. The latest dns.exe binary I can see for Windows Server 2003
is in:

887597 A DNS forwarder disappears after you restart the DNS Server service
in
http://support.microsoft.com/?id=887597

While this article isn't specific to your issue, it is the latest version
which will roll in all earlier code changes.

Another option may be to log an incident with PSS and have them track down
the cause of the issue with appropriate logging.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.



Blake said:
The memory usage of DNS.EXE also starts climbing and gets upwards of 67
Megabytes. I would understand if there was some memory utilization for
the DNS cache, but this seems excessive. DNS is not normally considered a
real intensive service.

I have considered re-loading one of these machines - do a clean install of
Win2k3 instead of an upgrade. I have also considered simply waiting for
SP1 to be released. Not sure what I should do.

Thanks

Blake

Mark Renoden said:
Hi Blake

I've seen a number of code revisions to dns.exe for Windows Server 2003
in the form of hotfixes but none of them have been to specifically
address the issue you're describing. It may be the case that in order to
track this down, you'd need to go through a reasonable degree of
debugging with PSS.

You might be experiencing this:

830381 Server Responsiveness Degrades and Queries Time Out When You Run
the DNS
http://support.microsoft.com/?id=830381

HTH
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no
rights.

Blake said:
Not a bad thought Kevin, but these boxes aren't forwarded to each other.

These 2 boxes are our 'public' DNS servers, and neither is forwarded.
(our internal DNS servers ARE forwarded to these 2)

I wasn't having any problems until these machines were upgraded to
Windows 2003. They ran with this DNS config for 3 years on Win2K.

Thanks
Blake

In Blake <[email protected]> commented
Then Kevin replied below:
My DNS servers (Win2k3 upgraded over Win2k) will run
flawlessly for several days/weeks. The CPU utlitization
will slowly climb until they get to a point where they
peg my processor. This happens on both boxes.

Is there a memory leak with the newest version of DNS
server? I have seen reports of this behavior in my web
searching but no solutions.

Both boxes?
Any chance the DNS on these two boxes are forwarding to each other?
If they are, then this will cause a DNS loop which results in your
behavior.
Do not forward two DNS servers to each other, always forward out to
another
DNS server that does not forward back in.
Click to expand...
Click to expand...
Click to expand...
 
Thanks, Mark.

I'll need to call MS to get that hotfix, correct?

Blake

Mark Renoden said:
Hi Blake

If you're considering a rebuild of a box anyway, it can't hurt to try the
latest dns.exe binary to see if the issue you've got has been fixed.
While not the approach you'd normally take with a production server, the
fact that you're considering a clean install lends itself to this test.

Not all code changes are documented and hotfix releases include all prior
code changes. The latest dns.exe binary I can see for Windows Server 2003
is in:

887597 A DNS forwarder disappears after you restart the DNS Server service
in
http://support.microsoft.com/?id=887597

While this article isn't specific to your issue, it is the latest version
which will roll in all earlier code changes.

Another option may be to log an incident with PSS and have them track down
the cause of the issue with appropriate logging.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no
rights.



Blake said:
The memory usage of DNS.EXE also starts climbing and gets upwards of 67
Megabytes. I would understand if there was some memory utilization for
the DNS cache, but this seems excessive. DNS is not normally considered
a real intensive service.

I have considered re-loading one of these machines - do a clean install
of Win2k3 instead of an upgrade. I have also considered simply waiting
for SP1 to be released. Not sure what I should do.

Thanks

Blake

Mark Renoden said:
Hi Blake

I've seen a number of code revisions to dns.exe for Windows Server 2003
in the form of hotfixes but none of them have been to specifically
address the issue you're describing. It may be the case that in order
to track this down, you'd need to go through a reasonable degree of
debugging with PSS.

You might be experiencing this:

830381 Server Responsiveness Degrades and Queries Time Out When You Run
the DNS
http://support.microsoft.com/?id=830381

HTH
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to
email me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no
rights.

Not a bad thought Kevin, but these boxes aren't forwarded to each
other.

These 2 boxes are our 'public' DNS servers, and neither is forwarded.
(our internal DNS servers ARE forwarded to these 2)

I wasn't having any problems until these machines were upgraded to
Windows 2003. They ran with this DNS config for 3 years on Win2K.

Thanks
Blake

In Blake <[email protected]> commented
Then Kevin replied below:
My DNS servers (Win2k3 upgraded over Win2k) will run
flawlessly for several days/weeks. The CPU utlitization
will slowly climb until they get to a point where they
peg my processor. This happens on both boxes.

Is there a memory leak with the newest version of DNS
server? I have seen reports of this behavior in my web
searching but no solutions.

Both boxes?
Any chance the DNS on these two boxes are forwarding to each other?
If they are, then this will cause a DNS loop which results in your
behavior.
Do not forward two DNS servers to each other, always forward out to
another
DNS server that does not forward back in.
Click to expand...
Click to expand...
Click to expand...
 
Hi Blake

Yeah that's right. Just contact support in your region and request the fix.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

Blake said:
Thanks, Mark.

I'll need to call MS to get that hotfix, correct?

Blake

Mark Renoden said:
Hi Blake

If you're considering a rebuild of a box anyway, it can't hurt to try the
latest dns.exe binary to see if the issue you've got has been fixed.
While not the approach you'd normally take with a production server, the
fact that you're considering a clean install lends itself to this test.

Not all code changes are documented and hotfix releases include all prior
code changes. The latest dns.exe binary I can see for Windows Server
2003 is in:

887597 A DNS forwarder disappears after you restart the DNS Server
service in
http://support.microsoft.com/?id=887597

While this article isn't specific to your issue, it is the latest version
which will roll in all earlier code changes.

Another option may be to log an incident with PSS and have them track
down the cause of the issue with appropriate logging.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no
rights.



Blake said:
The memory usage of DNS.EXE also starts climbing and gets upwards of 67
Megabytes. I would understand if there was some memory utilization for
the DNS cache, but this seems excessive. DNS is not normally considered
a real intensive service.

I have considered re-loading one of these machines - do a clean install
of Win2k3 instead of an upgrade. I have also considered simply waiting
for SP1 to be released. Not sure what I should do.

Thanks

Blake

Hi Blake

I've seen a number of code revisions to dns.exe for Windows Server 2003
in the form of hotfixes but none of them have been to specifically
address the issue you're describing. It may be the case that in order
to track this down, you'd need to go through a reasonable degree of
debugging with PSS.

You might be experiencing this:

830381 Server Responsiveness Degrades and Queries Time Out When You Run
the DNS
http://support.microsoft.com/?id=830381

HTH
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to
email me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no
rights.

Not a bad thought Kevin, but these boxes aren't forwarded to each
other.

These 2 boxes are our 'public' DNS servers, and neither is forwarded.
(our internal DNS servers ARE forwarded to these 2)

I wasn't having any problems until these machines were upgraded to
Windows 2003. They ran with this DNS config for 3 years on Win2K.

Thanks
Blake

message In Blake <[email protected]> commented
Then Kevin replied below:
My DNS servers (Win2k3 upgraded over Win2k) will run
flawlessly for several days/weeks. The CPU utlitization
will slowly climb until they get to a point where they
peg my processor. This happens on both boxes.

Is there a memory leak with the newest version of DNS
server? I have seen reports of this behavior in my web
searching but no solutions.

Both boxes?
Any chance the DNS on these two boxes are forwarding to each other?
If they are, then this will cause a DNS loop which results in your
behavior.
Do not forward two DNS servers to each other, always forward out to
another
DNS server that does not forward back in.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top