Link to home
Start Free TrialLog in
Avatar of ILoveLegos
ILoveLegos

asked on

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?
SOLUTION
Avatar of Henrik Johansson
Henrik Johansson
Flag of Sweden image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ILoveLegos
ILoveLegos

ASKER

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.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ok with me as I am ILoveLegos