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

Reuse a connection for multiple queries

04

Persistent connections amortize TCP and TLS establishment and support multiple exchanges.

Related RFCs and changes

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

DIAGRAM§ 3.4 ↗
RFC 7858 · § 3.4EXAMPLE
3 / 3
Reuse a connection for multiple queriesPersistent connections amortize TCP and TLS establishment and support multiple exchanges.One connection, many queriesquery A / response Aquery B / response Bidle closeA later exchange reestablishes transport after close
03
An idle close requires reestablishing before later queries.

An idle close requires reestablishing before later queries.

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

Avoid a new handshake for every DNS question when a connection is reusable.

  • Avoid a new handshake for every DNS question when a connection is reusable.
  • Idle close and reestablishment require resource and timeout management.
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 ↗