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.

Incorrect CNAME records on a Windows Server 2012 R2-based DNS server


View products that this article applies to.

Summary

This article describes an issue when achain of CNAME records is configured on a Windows Server 2012 R2-based DNS server. The issue is resolved in update rollup 2962409, or in hotfix 2955856 that is described in this article and has a prerequisite.

↑ Back to the top


Symptoms

Consider the following scenario:

  • You have a Windows Server 2012 R2-based Domain Name System (DNS) server configured to perform name resolutions.
  • The DNS server is configured to forward the request to resolve external domains.
  • A chain of CNAME records is configured on the DNS server.
In this scenario, the CNAME records that contain the DNAME records are returned incorrectly when the DNS server answers the queries from the clients or the applications.

↑ Back to the top


Resolution

To resolve this issue, install update rollup 2962409, or install the hotfix that is described in this article. 

Update information

For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:
2962409  Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: June 2014

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.

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 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 website: 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 first install the update 2919355 on Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014

Registry information

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

Restart requirement

You must restart the computer after you apply this hotfix.

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 2012 R2 file information and notes
  • The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.3.960 0.17xxxWindows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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 2012 R2
File nameFile versionFile sizeDateTimePlatform
Cache.dnsNot applicable3,19818-Jun-201314:43Not applicable
Dns.exe6.3.9600.171101,597,44028-Apr-201422:28x64
Dnsserver.events.xmlNot applicable60918-Jun-201314:43Not applicable

↑ 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.

↑ Back to the top


More Information

For more information about software update terminology, 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 file information

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File propertyValue
File nameAmd64_39f9c68e93592c05fc01a339aff3736c_31bf3856ad364e35_6.3.9600.17110_none_b9af2c1e24e8f50f.manifest
File versionNot applicable
File size710
Date (UTC)29-Apr-2014
Time (UTC)09:09
File nameAmd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.3.9600.17110_none_3f0bd938aa5695df.manifest
File versionNot applicable
File size190,922
Date (UTC)29-Apr-2014
Time (UTC)02:00

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2955856
Revision : 1
Created on : 1/7/2017
Published on : 6/10/2014
Exists online : False
Views : 277