DNS High CPU

[Guest Roger Waterhouse]

Windows Server 2003 SP2 on an HP ML350G3.It is a DC and general File and

Print Server. On a few weekends over the last 2 months the DNS server has

started using more and more CPU cycles until the system is extremely

unresponsive. This shuts down our email as the Exchange Server can't resolve

any addresses. I have searched for solutions with no luck. There are no

obvious entires in the event viewer and I'm just not sure what to do next.

 

Any suggestions welcomed.

 

Cheers

Roger

[Guest Chris]

RE: DNS High CPU

 

Hi Roger ,

 

You can start here : Although this doesn't say much :

 

 

Lookup KB830381

 

Does this sound like the issue you are having ?

 

Thanks

Chris

 

 

 

"Roger Waterhouse" wrote:

> Windows Server 2003 SP2 on an HP ML350G3.It is a DC and general File and

> Print Server. On a few weekends over the last 2 months the DNS server has

> started using more and more CPU cycles until the system is extremely

> unresponsive. This shuts down our email as the Exchange Server can't resolve

> any addresses. I have searched for solutions with no luck. There are no

> obvious entires in the event viewer and I'm just not sure what to do next.

>

> Any suggestions welcomed.

>

> Cheers

> Roger

[Guest Roger Waterhouse]

RE: DNS High CPU

 

Thanks Chris;

 

I don't think so as the time frame is much longer. Everything goes fine for

weeks and then suddenly this high cpu problem occurs. I spent most of today

running AD diagnostics and can find no problems.

 

"Chris" wrote:

> Hi Roger ,

>

> You can start here : Although this doesn't say much :

>

>

> Lookup KB830381

>

> Does this sound like the issue you are having ?

>

> Thanks

> Chris

>

[Guest Leythos]

Re: DNS High CPU

 

In article <BF632FD9-15C5-47EB-BB27-EC61845D4F85@microsoft.com>,

RogerWaterhouse@discussions.microsoft.com says...

> Windows Server 2003 SP2 on an HP ML350G3.It is a DC and general File and

> Print Server. On a few weekends over the last 2 months the DNS server has

> started using more and more CPU cycles until the system is extremely

> unresponsive. This shuts down our email as the Exchange Server can't resolve

> any addresses. I have searched for solutions with no luck. There are no

> obvious entires in the event viewer and I'm just not sure what to do next.

>

> Any suggestions welcomed.

 

Is the internal domain name also a public/valid external name?

 

I've seen IT people name a internal domain yourcompany.com and then find

that the external name of yourcompany.com is a valid external name and

then DNS was trying to replicate with the external DNS server at

yourcompany.com, causing an increase in DNS CPU time.

 

--

 

Leythos

- Igitur qui desiderat pacem, praeparet bellum.

- Calling an illegal alien an "undocumented worker" is like calling a

drug dealer an "unlicensed pharmacist"

spam999free@rrohio.com (remove 999 for proper email address)

[Guest Roger Waterhouse]

Re: DNS High CPU

 

 

 

"Leythos" wrote:

> In article <BF632FD9-15C5-47EB-BB27-EC61845D4F85@microsoft.com>,

> RogerWaterhouse@discussions.microsoft.com says...

> > Windows Server 2003 SP2 on an HP ML350G3.It is a DC and general File and

-snip-

> > Any suggestions welcomed.

>

> Is the internal domain name also a public/valid external name?

>

> I've seen IT people name a internal domain yourcompany.com and then find

> that the external name of yourcompany.com is a valid external name and

> then DNS was trying to replicate with the external DNS server at

> yourcompany.com, causing an increase in DNS CPU time.

>

> --

>

> Leythos

> - Igitur qui desiderat pacem, praeparet bellum.

> - Calling an illegal alien an "undocumented worker" is like calling a

> drug dealer an "unlicensed pharmacist"

> spam999free@rrohio.com (remove 999 for proper email address)

Yes the domain name is both internal and external. I wan't aware this was a

problem and actually thought that this was "split horizon" DNS, in other

words I have manually defined ip addresses on our network to have the same

name ie: http://www.domain.com as the external ips. What can be done to resolve this?

 

Cheers

Roger

>