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

Open a dedicated TLS transport

01

DNS over TLS normally connects to TCP port 853 and begins TLS before DNS messages.

Related RFCs and changes

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

DIAGRAM§ 3.1 ↗
RFC 7858 · § 3.1EXAMPLE
3 / 3
Open a dedicated TLS transportDNS over TLS normally connects to TCP port 853 and begins TLS before DNS messages.DNS clientresolver :853TCP connectTLS handshakeprotected DNSDNS starts only after TLS establishment
03
Send DNS inside the established TLS connection.

Send DNS inside the established TLS connection.

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

No DNS messages are sent before the TLS handshake completes.

  • No DNS messages are sent before the TLS handshake completes.
  • A dedicated service port differs from opportunistically upgrading a cleartext DNS message.
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
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗