DNS name resolution and DNSSEC validation fail in Windows Server 2012 R2

Applies to: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 StandardWindows Server 2012 R2 Essentials

This article describes problems that occur on a Domain Name System (DNS) server in Windows Server 2012 R2. A hotfix is available to resolve these problems. The hotfix has a prerequisite.

Symptoms


You experience one of the following problems on a computer that is running Windows Server 2012 R2.

Problem 1

Assume that a secondary DNS server accesses its list of the master DNS servers to obtain the most recent copy of a zone. In this situation, DNS name resolution fails because the zone is marked as expired on the secondary DNS server when the DNS zone is removed from a single master DNS server.

Note This problem occurs even if multiple master DNS servers are configured for the zone, and if the zone exists on all other master DNS servers.

Problem 2

Zones that are signed by using DNS Security Extensions (DNSSEC) do not validate correctly because the Resource Record Signature (RRSIG) for theStart of Authority(SOA) resource record is invalid on the secondary DNS server. Additionally, the invalid RRSIG causes the zone to be displayed as "bogus" in multiple DNSSEC validation tools on the web.

Problem 3

The DNS server is not following the section five: Caching Negative Answers of RFC 2308. Additionally, the server IP address is changed for the DNS record of one service server. Therefore, the stale records are not refreshed until the SOA's TTL (Time to Live) expires.

Note The exact rule that is being violated is as follows:
When the authoritative server creates this record its TTL is taken from the minimum of the SOA.MINIMUM field and SOA's TTL.

Hotfix information

Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.

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 have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.

Registry information

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

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Status


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

References


See the terminology that Microsoft uses to describe software updates.