Negative Caching of DNS Resolution Failures
RFC 9520

Received changes through RFC Editor sync (created document RFC 9520, created became rfc relationship between draft-ietf-dnsop-caching-resolution-failures and RFC 9520, set abstract to 'In the DNS, resolvers employ caching to reduce both latency for end users and load on authoritative name servers. The process of resolution may result in one of three types of responses: (1) a response containing the requested data, (2) a response indicating the requested data does not exist, or (3) a non-response due to a resolution failure in which the resolver does not receive any useful information regarding the data's existence. This document concerns itself only with the third type.

RFC 2308 specifies requirements for DNS negative caching. There, caching of TYPE 2 responses is mandatory and caching of TYPE 3 responses is optional. This document updates RFC 2308 to require negative caching for DNS resolution failures.

RFC 4035 allows DNSSEC validation failure caching. This document updates RFC 4035 to require caching for DNSSEC validation failures.

RFC 4697 prohibits aggressive requerying for NS records at a failed zone's parent zone. This document updates RFC 4697 to expand this requirement to all query types and to all ancestor zones.', set pages to 14, set standardization level to Proposed Standard, added RFC published event at 2023-12-22, created updates relation between RFC 9520 and RFC 2308, created updates relation between RFC 9520 and RFC 4035, created updates relation between RFC 9520 and RFC 4697)