Check cache lifetime and signature time
05TTL expiration and RRSIG validity periods solve different timing problems.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 8.1 ↗
RFC 4033 · § 8.1EXAMPLE
3 / 3
03
Do not accept data after the relevant validity constraint has failed.
Do not accept data after the relevant validity constraint has failed.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
RFC 2535 DNSSEC familyRFC 4033 § 10
The revised family separates introduction, record formats, and protocol behavior across RFCs 4033, 4034, and 4035.
Read the updated RFC section ↗TTL bounds cache reuse; signature inception and expiration bound signature validity.
- TTL bounds cache reuse; signature inception and expiration bound signature validity.
- A validator needs sufficiently correct time to assess signature validity.
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