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

Authenticate a missing name or type

03

DNSSEC must prove negative answers as well as existing records.

Related RFCs and changes

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

DIAGRAM§ 3.2 ↗
RFC 4033 · § 3.2EXAMPLE
3 / 3
Authenticate a missing name or typeDNSSEC must prove negative answers as well as existing records.Query: missing.example.a.example.z.example.signed NSEC denialAuthenticated absenceA plain NXDOMAIN alone is not a validated denial proof
03
Validate the denial before treating absence as authenticated.

Validate the denial before treating absence as authenticated.

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

NSEC provides authenticated denial of name or type existence in this document family.

  • NSEC provides authenticated denial of name or type existence in this document family.
  • A plain NXDOMAIN response without a validated proof does not establish authenticated absence.
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 ↗