I found Mr. Fekay's article on ADSI Edit and duplicate DNS zones very helpful. Using that guide, I located both InProgress and CNF zones which I was confident to delete.
These all replicated out and have not returned. But I am still getting event ID 4515 entries about once a month. I am pretty sure I have figured out what to do but would like to get some expert opinion to avoid stepping on any landmines. :)
The event 4515 text describes what is happening (I've redacted the actual domain name):
"The zone xxxx.local was previously loaded from the directory partition DomainDnsZones.xxxx.local but another copy of the zone has been found in directory partition ForestDnsZones.xxxx.local. The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible."
My replication scope is domain, not forest, on all DCs
As shown in the attached capture from ADSI Edit, my forest and domain containers both have a zone called xxxx.local (yellow highlights).
I believe this is a duplicate zone situation and one of these zones should be removed. But because these are not named InProgress or CNF, I hesitate.
The details pane shows data from the Forest copy and this zone has references to a site that was removed long ago called TB (circled in red). These references do not exist in the domain copy of this zone.
Considering the event ID details, the old AD site reference (in only the Forest copy) and my scope settings I believe I should delete the ForestDNSZone called xxxx.local.

So my specific questions are -
Is my reasoning correct about removing that zone?
If just right click and delete this zone will it safely stop the event ID 4515s or are there other actions I should take?
Will the deletion replicate around to the other DCs or will it need to be deleted manually on all DCs?
Any input is really appreciated.
Warmest regards..
@afekay





