Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You may receive an error message when you try to change the replication scope of a DNS zone on a DNS server that is a Windows Server 2003-based domain controller


View products that this article applies to.

Symptoms

On a Microsoft Windows Server 2003-based domain controller, you configure a Domain Name System (DNS) server and then create a DNS zone under Forward Lookup Zones. This DNS zone is integrated with the Active Directory directory service. You disconnect and rejoin the DNS zone to Active Directory. After you do this, you try to change the replication scope of the zone to all DNS servers in the Active Directory domain. In this case, you may not be able to reset the replication zone. Additionally, you may receive the following error message:
The replication scope could not be set. For more information, see "DNS zone replication in Active Directory" in Help and Support. The error was: The name limit for the local computer network adapter card was exceeded.

↑ Back to the top


Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

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, 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: 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. To create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" section and the online request forms display 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 must restart the 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, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Dns.exe5.2.3790.209423,42408-Sep-200418:56x86
Windows Server 2003, Itanium-based versions
File nameFile versionFile sizeDateTimePlatformService branch
Dns.exe5.2.3790.2091,025,02408-Sep-200406:25IA-64RTMQFE
Wdns.exe5.2.3790.209423,42408-Sep-200406:26x86WOW

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This feature was first included in Windows Server 2003 Service Pack 1.

↑ Back to the top


More information

Steps to reproduce this problem

1.Configure a DNS server on a Windows Server 2003-based domain controller.
2.Click Start, click Run, type dnsmgmt.msc, and then click OK.
3.Under Forward Lookup Zones, create a new Active Directory-integrated DNS zone. For example, create a DNS zone named inet.contoso.com.
4. Right-click inet.contoso.com, and then click Properties.
5. Click Change to change the DNS zone type.
6. Click to clear the Store the zone in Active Directory check box, click OK, and then click Yes.
7.In the property dialog box for inet.contoso.com, click Apply.
8.Click Change to change the DNS zone type.
9.Click to select the Store the zone in Active Directory check box, click OK, and then click Yes.
10. Click Change to change the DNS zone replication scope.
11.Click To all DNS servers in the Active Directory domain contoso.com, and then click OK.
12.In the zone property dialog box, click OK.
For more 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

↑ Back to the top


Keywords: KB875520, kbpubtypekc, kbfix, kbbug, kbwinserv2003presp1fix, kbhotfixserver, kbqfe, kbautohotfix

↑ Back to the top

Article Info
Article ID : 875520
Revision : 10
Created on : 7/24/2007
Published on : 7/24/2007
Exists online : False
Views : 269