Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4515
Time: 12:45:22 PM
The zone 'domain' was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition DomainDnsZones.domain.com.
The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible.
If an administrator has moved this zone from one directory partition to another this may be a harmless transient condition. In this case, no action is necessary. The deletion of the original copy of the zone should soon replicate to this server.
If there are two copies of this zone in two different directory partitions but this is not a transient caused by a zone move operation then one of these copies should be deleted as soon as possible to resolve this conflict.
To change the replication scope of an application directory partition containing DNS zones and for more details on storing DNS zones in the application directory partitions, please see Help and Support.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp
0000: 89 25 00 00 ‰%..
Looking through this MS article, http://support.microsoft.com/kb/867464
, I found some helpful stuff.
I know there is a duplicate located at the location noted in 'Option' 3 of this article, "Domain NC > CN=MicrosoftDNS shown in ADSIEDIT. This is obviously the one being used because its data up to date while the other, located in 'DC=DomainDNSZones,DC=doma
in,DC=com > CN=MicrosoftDNS' as noted in option 2 of the same article.
The article also goes on to say that the first 2 options are the preferred since they are supported only by Win2003 domains, which mine is. However, if I delete the zone in question I fear all DNS data will be lost.
Is there a better way to go about rectifying this otherwise annoyance?