| Event Id | 1226 |
| Source | NTDS Replication |
| Description | The following object was created on a remote domain controller with an object name that already exists on the local domain controller. Object: CN=MicrosoftDNS,DC=DomainDnsZones,DC=Domain_Name,DC=com Object GUID: ff4bb5db-5fcc-4afe-b936-5836ea0d5315 Existing object GUID: 9d0fcccc-ee26-4818-b24c-8b0e6fa0173f. The object with the following GUID will be renamed since the other object had this name more recently. |
| Event Information | According to Microsoft: CAUSE: This problem occurs when a MicrosoftDNS container is created before a full replication of the application partition. The MicrosoftDNS container for the local domain is the most recent container. When replication occurs, the local MicrosoftDNS container replaces the remote MicrosoftDNS container and then renames the existing remote MicrosoftDNS container as a conflict object. RESOLUTION: A supported hotfix is now available from Microsoft, but it is only intended to correct the problem. Only apply it to systems that are experiencing this specific problem. You do not have to restart your computer after you apply this hotfix. |
| Reference Links | A MicrosoftDNS container is created before full replication and causes a DNS conflict 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.