A new Request for Comments is now available in online RFC libraries.
RFC 9520
Title: Negative Caching of DNS Resolution Failures
Author: D. Wessels,
W. Carroll,
M. Thomas
Status: Standards Track
Stream: IETF
Date: December 2023
Mailbox: [email protected],
[email protected],
[email protected]
Pages: 14
Updates: RFC 2308, RFC 4035, RFC 4697
I-D Tag: draft-ietf-dnsop-caching-resolution-failures-08.txt
URL: https://www.rfc-editor.org/info/rfc9520
DOI: 10.17487/RFC9520
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.
This document is a product of the Domain Name System Operations Working Group
of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
