RFC 9520: Negative Caching of DNS Resolution Failures
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9520
- Published
- December 2023
- Authors
- D. Wessels; W. Carroll; M. Thomas
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9445RADIUS Extensions for DHCP-Configured ServicesCurrent
August 2023
- RFC 9364DNS Security Extensions (DNSSEC)Current
February 2023
- RFC 9715IP Fragmentation Avoidance in DNS over UDPCurrent
January 2025
- RFC 9726Operational Considerations for Use of DNS in Internet of Things (IoT) DevicesCurrent
March 2025
- RFC 9276Guidance for NSEC3 Parameter SettingsCurrent
August 2022
- RFC 9803Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) ValuesCurrent
June 2025
- RFC 9224Finding the Authoritative Registration Data Access Protocol (RDAP) ServiceCurrent
March 2022
- RFC 9824Compact Denial of Existence in DNSSECCurrent
September 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?