On a computer that is running Windows Server 2008 or Windows Vista, you cannot add one or more servers to the securelist of a DNS service instance that is hosted on a server that is running Windows 2000 or Windows Server 2003

Consider the following scenario:

• You install the Microsoft Remote Server Administration Tools on a computer that is running Windows Vista or Windows Server 2008.
• From this computer, you use the Dnscmd.exe tool or the DNS Management Microsoft Management Console (MMC) snap-in. You use one of these tools to manage a DNS service instance that is hosted on a server that is running Windows 2000 or Windows Server 2003.
• You try to add some secondary servers to the "allowed zone transfer server" list (securelist) of a primary DNS server zone.

In this scenario, the secondary servers are not added to the securelist as expected. Additionally, the symptoms that appear for this problem depend on the number of IP addresses that you try to add to the securelist. The following are the symptoms that may appear:

• If you try to add more than one IP address, the operation fails.
• If you try to add only one IP address of a secondary server, the operation seems to complete successfully. However, the operation adds an address of 1.0.0.0 to the securelist, instead of the expected IP address.

For example, you try to add a "4.1.1.1" server and a "4.2.2.2" server to the securelist by using the following command:In this case, you receive the following error message:If you try to add only the "4.1.1.1" server to the securelist by using the following command, an IP address of "1.0.0.0" is incorrectly added to the securelist instead of the "4.1.1.1" address:However, in this case, you receive no error message.

This problem occurs because Windows Server 2008 and Windows Server 2003 use different structures to store the securelist. Additionally, the conversion mechanism does not make correct translation between these different structures.

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

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 the problem described in this article. 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

To apply this hotfix, the computer must be running one of the following operating systems:

• Windows Server 2008
• Windows Server 2008 Service Pack 2 (SP2)
• Windows Vista Service Pack 1 (SP1)
• Windows Vista Service Pack 2 (SP2)

Additionally, the computer must have the DNS server tool or the Remote Server Administration Tools installed.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other hotfix.

File information

The Global 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 item in Control Panel.

Windows Vista and Windows Server 2008 file information note

• The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

  Version	Product	SR_Level	Service branch
  6.0.6000.16xxx	Windows Vista	RTM	GDR
  6.0.6000.20xxx	Windows Vista	RTM	LDR
  6.0.6001.18xxx	Windows Vista and Windows Server 2008	SP1	GDR
  6.0.6001.22xxx	Windows Vista and Windows Server 2008	SP1	LDR
  6.0.6002.18xxx	Windows Vista and Windows Server 2008	SP2	GDR
  6.0.6002.22xxx	Windows Vista and Windows Server 2008	SP2	LDR

• Service Pack 1 is integrated into the original release of Windows Server 2008.
• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

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

To work around this issue, make sure that the operating system that is running the DNS management tools is the same as the operating system that is hosting the DNS service instance.

For example, you want to manage a DNS service instance that is hosted on a computer that is running Windows Server 2003. To work around this issue in this example, use the Dnscmd.exe tool or the DNS Management Microsoft Management Console (MMC) snap-in from another computer that is also running Windows Server 2003.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista