Validation fails for some DNSSEC-signed zones in a Windows Server 2012 R2 environment

Consider the following scenarios:
  • When a Windows Server 2012 R2-based DNS server is enabled for domain name system security extensions (DNSSEC) validation, the DNS server may not always resolve some DNSSEC-signed zones. For example, when the DNS server receives a request to resolve a host name in a DNSSEC-signed zone, the DNS server returns a SERVFAIL error to the client.

  • A server that is running Windows Server 2012 R2 is used as an upstream forwarder for DNSSEC queries. In this case, when the Windows Server 2012 R2 forwarder DNS server does not receive DNSSEC records in a certain order, it cannot cache the full record list, and replies to the validating DNS server are incomplete. This causes DNSSEC validation to fail. This behavior occurs when a BIND server is used to return DNSSEC records to the Windows Server 2012 R2 forwarder.


Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to 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.


To apply this update, you must first have update 2919355 installed in Windows Server 2012 R2.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information

The English (United States) 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

Important Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" 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 8.1" 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, 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.17 xxxWindows 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 for Windows 8.1 and Windows Server 2012 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 2012 R2
File nameFile versionFile sizeDateTimePlatform
Cache.dnsNot Applicable3,19818-Jun-201314:43Not Applicable
Dns.exe6.3.9600.176311,733,63212-Jan-201501:37x64 Applicable60918-Jun-201314:43Not Applicable

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File nameAmd64_3b6d1ec6222173bff5f67987c4d5cf6b_31bf3856ad364e35_6.3.9600.17634_none_20af599b9f7b0d62.manifest
File versionNot Applicable
File size710
Date (UTC)15-Jan-2015
Time (UTC)07:45
File nameAmd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.3.9600.17634_none_3efa4406aa6324e0.manifest
File versionNot Applicable
File size287,325
Date (UTC)15-Jan-2015
Time (UTC)02:47
File namePackage_1_for_kb3014171~31bf3856ad364e35~amd64~~
File versionNot Applicable
File size1,832
Date (UTC)15-Jan-2015
Time (UTC)07:45
File namePackage_for_kb3014171_rtm_gm~31bf3856ad364e35~amd64~~
File versionNot Applicable
File size1,413
Date (UTC)15-Jan-2015
Time (UTC)07:45
File namePackage_for_kb3014171_rtm~31bf3856ad364e35~amd64~~
File versionNot Applicable
File size1,465
Date (UTC)15-Jan-2015
Time (UTC)07:45
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.

Article ID: 3014171 - Last Review: 10/01/2015 18:54:00 - Revision: 3.0

Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard

  • kbqfe kbfix kbexpertiseinter kbsurveynew kbbug kbautohotfix kbHotfixServer KB3014171