DNS taking 45 minutes to start

[darahw]

Hello.

We are running W2K3 with AD across our network. We have DC's at each location. At our hosted datacenter we have a 2003 AD server running DNS. Each one of the offices runs DNS on their AD server.
We suddenly started having the problem that the datacenter AD/DNS server can't get out. In event viewer there were event id- 4000 listed. This suddenly happened for the first time Saturday night.

Does anyone have any ideas what this might be?

When the server is restarted - it is a good 45 minutes before another server at the datacenter can see the network.

The ad/dns server points to itself for DNS.

Thanks in advance!!

 

[tfg13]

What changes to the network took place Saturday night? Any firewall/router changes you are aware of? Any ISP changes that you are aware of?

Any of these symptoms solve your issue?

http://support.microsoft.com/default.aspx?scid=kb;en-us;316685

 

[darahw]

That is the strange thing- there were no changes done Saturday night.

45 minutes for DNS to come up on that server is a long time, isn't it?

 

[tfg13]

Any of the fixes in the link help you out?

 

[darahw]

No- none of these are our problem.

 

[tfg13]

Are you still receiving event id 4000? Or, are they different numbers now?

 

[Spirit]

I guess you only have the one DNS server at the site?

Get a new DNS server out to the data centre.

You could also try reinstalling IP on the DNS server.

Anyone been playing with the permissions on the system?

Can you post the entire 4000 message?