A MicrosoftDNS container is created before full replication and causes a DNS conflict in Windows Server 2003

When you promote a Microsoft Windows Server 2003-based computer to a domain controller, an Active Directory conflict may occur on the remote replica MicrosoftDNS container. The remote replica MicrosoftDNS container is renamed, and the new MicrosoftDNS container contains only the RootDNSServers zone.

The DNS server log for the promoted domain controller may contain events that are similar to the following:

Event Type: Information
Event Source: DNS
Event Category: None
Event ID: 4502
Description:
The DNS added the local Active Directory to the replication scope of Application Directory Partition DomainDnsZones.Domain_Name. The distinguished name of the root of this Directory Partition is DC=DomainDnsZones,DC=Domain_Name,DC=com.

Event Type: Information
Event Source: DNS
Event Category: None
Event ID: 708
Description:
The DNS server did not detect any zones of either primary or secondary type during initialization. It will not be authoritative for any zones, and it will run as a caching-only server until a zone is loaded manually or by Active Directory replication. For more information, see the online Help.

On the remote domain controller, you may see an event that is similar to the following:

Event Type: Information
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1226
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.

Object GUID:
ff4bb5db-5fcc-4afe-b936-5836ea0d5315 Renamed object name: MicrosoftDNS CNF:ff4bb5db-5fcc-4afe-b936-5836ea0d5315

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.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, 32-bit editions

Windows Server 2003, 64-Bit Edition

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: