Windows Forum

Ask something
Discussion Locked

DNS event error 4004 on boot, root zone.

0 helpful
4 replies

by m.r. 3 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Our W2K server has been up for over a year and was upgraded from NT4 PDC to become a W2K domain. We always get event ID 4004 when booting but were told it's normal as it's the only W2K domain controler and dns server. It recently became more of anissue as we would like to setup forwarders and per MS article removed the root zone. Upon doing this we can no longer connect to AD. There is both a forward and reverse zone for the domain that seem to be populated properly. We have not rebooted yet and that may be the key but wanted more info before making changes. Any thoughts or questions? Thanks in advance.

4 replies

by maxwell edison

A 4004 error generally means that a domain has not been properly registered or propagated. In you case, I would suspect that Windows 2000 DNS has not been properly integrated with AD.

Look at this article on integrating DNS with AD. It may provide some configuration help. It's very thorough and nicely illustrated.

http://www.naspa.com/PDF/2000/1100%20TS%20PDFs/T0011002.pdf

(REMOVE SPACES from the pasted URL.)

Also look at Microsoft article Q232690 titled, "Urgent Replication Triggers in Windows 2000"

http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q232690&

(REMOVE SPACES from the pasted URL.)

I wish I could provide more specific help, but hopefully these articles will provide a clue that will lead you in the right direction.

Good luck,

Maxwell

by shanghai sam

Thanks as well. I subscribe to NaSPA and that is a short and simple article but those steps were followed at setup so I'm not sure where it has gone wrong. I'm not sure how the MS article applies. Has anyone ever pulled DNS off a live domain and recreated it?

This discussion is closed to new replies.