Visual RFC.
ALL RFCs / RFC 8484
Read the RFC ↗
RFC 8484 / PROTOCOL MECHANISMS

Respect DNS TTL and HTTP cache age

04

HTTP caching must not extend the underlying DNS data’s usable lifetime.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 5.1 ↗
RFC 8484 · § 5.1EXAMPLE
3 / 3
Respect DNS TTL and HTTP cache ageHTTP caching must not extend the underlying DNS data’s usable lifetime.Original DNS TTL: example 300 sHTTP Age: 100 sRemaining lifetime: 300 − 100 = 200 sA shared HTTP cache has already consumed part of the lifetime
03
Reduce the remaining DNS lifetime by the age already elapsed.

Reduce the remaining DNS lifetime by the age already elapsed.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

A client accounts for the HTTP Age value when determining remaining DNS lifetime.

  • A client accounts for the HTTP Age value when determining remaining DNS lifetime.
  • A cached response can be older than the moment it was received locally.
DETAILS

The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Choose the HTTPS resolver endpoint
  2. Send DNS using GET or POST
  3. Read HTTP and DNS errors separately
  4. Respect DNS TTL and HTTP cache age
  5. Understand who can still observe queries
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗