DNS zone trouble after demotion of AD server

[mofusjtf]

I just recently migrated AD from a W2k server to a W2k3 server. The migration went fine. About a week later I demoted the W2k server and the role transfer went fine but I'm having some intermittent DNS erros. Periodically (once a week) the DNS server service has to be restarted. The logs also indicate DNS ZONE sync errors from the old W2k server. DNS is configured correctly and operates normally but it appears that when it attempts to load the zone from the old server the service needs to be restarted. It shouldn't be trying to transfer the zone anymore since the old server is offline now. Any ideas would be a great help.

 

[porkchopexpress]

I'd run Netdiag and DCDiag and see what results you get to start.

Netdiag

http://www.microsoft.com/downloads/...14-7E6C-46E5-8C8C-3C439A732E9F&displaylang=en

DCdiag

http://www.microsoft.com/downloads/...87-8422-408C-9375-2D9AAF939FA3&displaylang=en

 

[itsp1965]

Was DNS installed on the recently demoted DC? Is the demoted server still online and possibly running DNS. It could be possible it still trying to communicate if the zone is still configured as AD integrated (on the demoted server)

 

[pagy]

Perhaps the old server is still on the name server lists and servers want to tranfer dns zones to it, or perhaps zones are only allowed to transfer to certain servers??

Check the above bits on the zone tranfers tab and name servers on the properties of the zone

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[mofusjtf]

ITSP1965, yes DNS was installed and running on the old (demoted) server. I did not uninstall DNS, I simply demoted the server and then turned it off. I could still power the server back on.

 

[itsp1965]

Just because the server is offline doesn't mean that the other AD DNS integrated servers are still not trying to communicate. As per what myself and Pagy have indicated, check the DNS settings on your other DNS boxes to ensure that they are not requesting zone transfers to the server that is offline

 

[Davetoo]

I was under the impression that in order for DNS to function it has to be on a DC. Is this not correct? When you DCPROMO a DNS server will it not remove the DNS from it?

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

 

[itsp1965]

DNS could function in any mode AD integrated, standard primary/secondary, etc. Doesn't have to be installed on a DC in order to work. AD integrated zones require the presence of an AD environment but you can run AD on conventional primary and secondary DNS roles
The DNS service is independent of AD, therefore DCPromo will not remove/disable the service.

 

[mofusjtf]

ITSP1965, the Zone properties do infact have the old DNS server listed as well as the new DNS (name) server listed.

Davetoo, AD does need DNS but they do not have to run on the same box but typically that is what I have seen. I would have though demoting the old server would have removed DNS but that does not appear to be the case.

How do I properly remove the old DNS server from the network? Do I simply turn the old server on and uninstall DNS?

 

[itsp1965]

In DNS right click on your DNS zone and select properties. Since the server is offline now.. go to the Name Servers tab and have the server removed

 

[pagy]

I would have though demoting the old server would have removed DNS but that does not appear to be the case.

I used to think so as well but there was a thread here not too long ago about that and some people suggested that removing the dns service from a dc before demoting it was the best thing to do.

Also possible is that someone explicitly added the server under the names server tab, perhaps when it didn't actually have to be there....

either way follow what itsp1965 says and remove it from the name servers tab and you should be done.

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[mofusjtf]

I resolved this issue by disabling Round Robin DNS. Since disabling this; i have not had to restart the DNS server.