- 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 informationA 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.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any previously released hotfix.
Article ID: 3014171 - Last Review: Oct 1, 2015 - Revision: 1