Technology and engineering · 2023

RFC 9520: Negative Caching of DNS Resolution Failures

by D. Wessels, W. Carroll, M. Thomas

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 requ

Anyone can see what's on the shelves. Open a book with a free account, and stay in touch with its book club.

First published
2023
Status
Proposed Standard
Pages
14
Copyright
✓ Free to read · Copied in full, as published

Where it comes from

RFC Editor · IETF Datatracker · IETF Trust Legal Provisions

Copied in full and unchanged from the RFC Editor, with the RFC's own notices. © IETF Trust and the persons identified as the document authors. The IETF Trust allows copying and distributing an RFC in full and without modification, so Micwyn shows it exactly as published and makes no study guide, audio or other version of it.

Discuss a passage

Select any passage in the reader and press Discuss to talk about it in public.

Join free to discuss a passage

Ask Micwyn about this book

Join (free) to ask about a PDF
Try asking

If you like this one