DNS Event 4515 deleting Zones and MSTID 867464

We are receiving the DNS Event error 4515 on DC restart. Our Domain is a single domain. We have used TID 867464. For Option 1 - ForestDNSZones, nothing displays beyond CN=LostandFound and CD=NTDSQuotas. For Option 2 - DomainDNSZones, there is a CN=MicrosoftDNS, and under that were two records listing our domain, such as contoso.com and contoso.com/cnf-333-3333-3333-33333. We deleted the 2n'd record on one DC, and followed the rest of the instructions to restart services and restart DNS. We ran the process on only one of our DCs and did not stop any DC replication when the 2nd record was deleted. After waiting approx. 1 hour, replication removed the 2nd record from the DomainDNSZones/MicrosoftDNS listing, however, on restart, the DC from which the deletion was started still displays the same error. What step have we missed?
ILoveLegosAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Henrik JohanssonSystems engineerCommented:
See eventid.net for some possibly solutions for your problem.
http://www.eventid.net/display.asp?eventid=4515&eventno=3593&source=DNS&phase=1
0
ILoveLegosAuthor Commented:
A little bit more information for you..we have discovered that our DNS replication is set to "all domain controllers in the AD domain", instead of the default 2003 of "all DNS servers in the AD domain". We do not have, in the DNS Console, _msdcs as a DNS application partion, but as a regular "folder" under "contoso.com" zone. Would changing the zone replication scope automatically, or magically, fix everything....by which I mean...create _msdcs.contoso.com as a separate zone under Forward Lookup Zones, and would we then see with ADSIEDIT, under dc=forestdnszones,dc=contoso,dc=com, a newly created cn=microsoftdns with the dc=_msdns.contoso.com.....  or do you think in this case we might have to manually create _msdns.contoso.com? I would imagine you would recommend following the steps to stop DNS services and work the problem with one DNS system first, as was suggested in the link you forwarded.
0
ILoveLegosAuthor Commented:
This is the answer that matches the problem we are having. Truely, we dio have a "that guy" here. We love our "that guy", so no one is taking a walk, just working the problem.

http://blogs.technet.com/networking/archive/2008/08/08/don-t-be-that-guy-the-case-of-the-missing-dns-zone.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ILoveLegosAuthor Commented:
ok with me as I am ILoveLegos
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.