DNS Server service does not respond to a CNAME query in the GlobalNames zone correctly in Windows Server 2008 or Windows Server 2008 R2

Consider the following scenario:

• You install the DNS Server role on a computer that is running Windows Server 2008 or Windows Server 2008 R2.
• You deploy a GlobalNames zone on the DNS server.
• You create a name with an alias (CNAME) record in the GlobalNames zone that has a fully qualified domain name (FQDN) for a target host zone that is not located on the local DNS server.
• The CNAME is the same as the first label of the target FQDN.

In this scenario, the DNS server responds with "Unspecified error" for any name resolution query for the CNAME record after the first successful response.

Here is a sample scenario:

• You deploy a GlobalNames Active Directory integrated DNS zone in a forest that has Windows Server 2008 R2 domain controllers.
• You create a "testa.domain.com" Active Directory integrated DNS zone only on domain controllers in the "testa" domain.
• You create a "testbb.globalnames CNAME testbb.testa.domain.com" record.
• You create a "testbb.testa.domain.com A 1.1.1.1" record.
• You connect to a Windows Server 2008 R2-based domain controller in another domain in this forest by using the Nslookup.exe utility.
• You try to resolve the "testbb.globalnames" name.

In this scenario, the DNS server responds with the correct IP address "1.1.1.1" in the first query. Then, it responds with "Unspecified error" in successive queries.

This issue occurs because the DNS Server service does not respond to the name resolution query correctly when the GlobalNames zone CNAME label is the same as the first label of the target FQDN.

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 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, you must be running one of the following operating systems:

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

Additionally, the DNS Server role must be installed.

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base: For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You do not need to restart the computer after you apply this hotfix. However, you have to stop the DNS Server service before you install this hotfix to avoid restarting.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 file information notes

Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

• 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.600 2 . 22xxx	Windows Server 2008	SP2	LDR

• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008

For all supported x64-based versions of Windows Server 2008

Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

• 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.1.760 0 . 21xxx	Windows Server 2008 R2	RTM	LDR
  6.1.760 1 . 21xxx	Windows Server 2008 R2	SP1	LDR

• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2008 R2

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

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: For more information about how to deploy a GlobalNames zone, visit the following Microsoft website:

Additional file information

Additional file information for Windows Server 2008

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

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

Additional file information for Windows Server 2008 R2

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