Microsoft KB Archive/836534

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

Article ID: 836534

Article Last Modified on 7/24/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise x64 Edition

-





SYMPTOMS
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. . The distinguished name of the root of this Directory Partition is DC=DomainDnsZones,DC= ,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= ,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



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.



Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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
  Date         Time   Version            Size    File name --  06-Feb-2004  15:53  5.2.3790.125      422,912  Dns.exe

Windows Server 2003, 64-Bit Edition
  Date         Time   Version            Size    File name --  06-Feb-2004  14:11  5.2.3790.125    1,023,488  Dns.exe 06-Feb-2004 14:53  5.2.3790.125      422,912  WDns.exe



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



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

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: replica multimaster ad lookup

Keywords: kbhotfixserver kbqfe kbhotfixserver kbqfe kbbug kbfix kbqfe kbwinserv2003presp1fix KB836534

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.