metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 8767: Serving Stale Data to Improve DNS Resiliency

In plain English — editorial summary, not part of the RFC

This document defines a method (serve-stale) for recursive resolvers to use stale DNS data to avoid outages when authoritative nameservers cannot be reached to refresh expired data. One of the motivations for serve-stale is to make the DNS more resilient to DoS attacks and thereby make them less attractive as an attack vector. This document updates the definitions of TTL from RFCs 1034 and 1035 so that data can be kept in the cache beyond the TTL expiry; it also updates RFC 2181 by interpreting values with the high-order bit set as being positive, rather than 0, and suggests a cap of 7 days.

Document record

Document ID
RFC8767
Published
March 2020
Authors
D. Lawrence; W. Kumari; P. Sood
Status
PROPOSED STANDARD
Stream
IETF
Area
ops
Pages
12
Also known as
—
Updates:
RFC 1034, RFC 1035, RFC 2181

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/8767-serving-stale-data-to-improve-dns-resiliency