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

Distinguish transport privacy from DNS data trust

05

DoT protects a particular connection; it does not make a dishonest resolver honest.

Related RFCs and changes

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

DIAGRAM§ 8 ↗
RFC 7858 · § 8EXAMPLE
3 / 3
Distinguish transport privacy from DNS data trustDoT protects a particular connection; it does not make a dishonest resolver honest.clientresolverresolver sees questionDNSSEC data proofseparate checkChannel privacy and DNS data authenticity cover different things
03
Use DNSSEC validation separately when authenticating DNS data.

Use DNSSEC validation separately when authenticating DNS data.

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

The selected resolver still sees the queries.

  • The selected resolver still sees the queries.
  • DNSSEC data authentication and TLS channel protection cover different boundaries.
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. Open a dedicated TLS transport
  2. Authenticate the intended resolver
  3. Frame DNS messages inside the stream
  4. Reuse a connection for multiple queries
  5. Distinguish transport privacy from DNS data trust

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 ↗