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

Follow a chain of trust

02

A validator starts with a configured trust anchor and follows authenticated delegations.

Related RFCs and changes

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

DIAGRAM§ 2 ↗
RFC 4033 · § 2EXAMPLE
3 / 3
Follow a chain of trustA validator starts with a configured trust anchor and follows authenticated delegations.configured trust anchorparent DS → child DNSKEYchild RRset + signatureEach link must authenticate the next; a key alone is not trust
03
Use the authenticated child key to validate the child RRset.

Use the authenticated child key to validate the child RRset.

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

A DS links a parent delegation to a child key; DNSKEY and signatures complete validation.

  • A DS links a parent delegation to a child key; DNSKEY and signatures complete validation.
  • An unsigned delegation and a bogus signed answer are different outcomes.
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

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗