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

Verify a signed record set

01

DNSSEC authenticates the origin and integrity of DNS RRsets, not a server’s transport connection.

Related RFCs and changes

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

DIAGRAM§ 3.1 ↗
RFC 4033 · § 3.1EXAMPLE
3 / 3
Verify a signed record setDNSSEC authenticates the origin and integrity of DNS RRsets, not a server’s transport connection.RRset + RRSIGDNSKEYsignature checkAlternative: changed RRsetAuthentic DNS data is still readable; signed is not encrypted
03
A changed covered record fails verification.

A changed covered record fails verification.

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

An RRSIG covers an RRset and is verified using an appropriate DNSKEY.

  • An RRSIG covers an RRset and is verified using an appropriate DNSKEY.
  • Authenticity does not provide confidentiality or stop denial of service.
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. Verify a signed record set
  2. Follow a chain of trust
  3. Authenticate a missing name or type
  4. Protect the last hop separately
  5. Check cache lifetime and signature time
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗