| Event Id | 4515 |
| Source | DNS |
| Description | The zone <domain.com> was previously loaded from the directory partition DomainDnsZones.<domain.com> but another copy of the zone has been found in directory partition ForestDnsZones.<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. |
| Event Information | According to Microsoft: CAUSE : This behavior occurs when the contoso.com zone exists in more than one location in Active Directory. For example, this can be a side effect of actions such as trying to move the zone from one directory partition to another. RESOLUTION : To resolve this behavior, determine which Active Directory partition for contoso.com you would like to use, and then remove the other contoso.com zone(s) from Active Directory. There are three default directory partition locations in Active Directory that DNS can be stored in on a Windows 2003 Domain Controller (DC). These are: 1. To all DNS servers in the Active Directory Forest contoso.com. [ForestDNSZones] 2. To all DNS servers in the Active Directory domain contoso.com. [DomainDNSZones] 3. To all domain controllers in the Active Directory domain contoso.com. User Action : If you recently moved a zone or changed the replication scope of a zone, for example from forest wide to domain wide, this event can be ignored. If this is not the case, resolve the conflict by removing one of the zones. This information from some newsgroups may help you: ------------------------------------------------------------------------------ In a Windows Server 2003 domain, changing the replication scope using the DNS snap-in can cause this error. It may only happen once, but if it repeats, the old copy might not have been deleted. When this happens, use ADSI Edit from the Windows Support Tools to delete the duplicate. To get to the necessary partition, such as DomainDNSZones, you must tell ADSI to use a custom connection point of DC=DomainDNSZones,DC=domain,DC=com. You cannot see this partition using any of the default well-known naming contexts. ------------------------------------------------------------------------------ |
| Reference Links | The zone %1 was previously loaded from the directory partition %2 but another copy of the zone has been found in directory partition %3. Event ID 4515 is logged in the DNS Server log in Windows Server 2003 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.