Protocols
Saved & recent

DNS over TLS

Also called: DoT, DNS privacy, encrypted DNS over TLS

DNS over TLS, or DoT, carries DNS messages over a dedicated TLS-protected connection, normally using TCP port 853. After establishing TLS, the client and resolver exchange DNS messages with length framing. Authenticating the resolver is essential when the client requires protection against an active attacker impersonating it.

For example, a device can keep a TLS connection open to its configured recursive resolver and send several queries through it. A local network observer cannot simply read those DNS messages, but the chosen resolver still can. DoT protects that connection; it does not encrypt the entire recursive lookup chain or replace DNSSEC validation. DoH carries DNS through HTTPS instead of this dedicated transport.

Read first
DNS, TLS
Related
DNS over HTTPS, DNSSEC, Transport port
Further reading
IETF RFC 7858 — Specification for DNS over Transport Layer Security (TLS)
client recursive resolver authoritative DNS TLS first · TCP 853 separate upstream DNS endpoint authenticated two length-prefixed DNS messages length DNS message 1 length DNS message 2 within client–resolver TLS DNSSEC · separate data validation
Illustrative DoT connection: multiple framed DNS exchanges share an authenticated TLS channel to the selected resolver.

View in the full Protocols collection