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 2Zones that are signed by using DNS Security Extensions (DNSSEC) do not validate correctly because the Resource Record Signature (RRSIG) for the
Start 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 3The 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.