DNS over TLS (DoT, RFC 7858) carries ordinary DNS messages inside a TLS session, by convention on TCP port 853. It gives the same confidentiality and tamper protection against on-path attackers that HTTPS gives web traffic, but without the HTTP layer.
Why it matters
Because DoT uses its own port, network administrators can easily see, allow or block it, which is a key difference from DNS over HTTPS, where DNS hides among normal web traffic. Android's "Private DNS" feature uses DoT, and many resolvers and forwarders such as Unbound support it. Like DoH, it protects the link to your resolver only. It does not authenticate the records themselves.
Example
Test a DoT resolver with kdig from the Knot tools:
kdig -d @1.1.1.1 +tls-host=cloudflare-dns.com +tls example.com A
An Unbound forwarder setting looks like:
forward-zone:
name: "."
forward-tls-upstream: yes
forward-addr: 1.1.1.1@853#cloudflare-dns.com
Common mistakes
- Blocking outbound port 853 in a firewall and then wondering why Private DNS fails on phones.
- Skipping certificate name validation, which leaves the connection open to impersonation.
- Confusing it with DNSSEC, which signs the data.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.