DNS over TLS

BIND supports DoT connections as of version 9.17.^[3] Earlier versions offered DoT capability by proxying through stunnel.^[4] Unbound has supported DNS over TLS since 22 January 2023.^[5][6] Unwind has supported DoT since 29 January 2023.^[7][8] With Android Pie's support for DNS over TLS, some ad blockers now support using the encrypted protocol as a relatively easy way to access their services versus any of the various work-around methods typically used such as VPNs and proxy servers.^{[9][10][11][12]}

Android clients running Android Pie or newer support DNS over TLS and will use it by default if the network infrastructure, for example the ISP, supports it.^[13][14]

In April 2018, Google announced that Android Pie will include support for DNS over TLS,^[15] allowing users to set a DNS server phone-wide on both Wi-Fi and mobile connections, an option that was historically only possible on rooted devices. DNSDist, from PowerDNS, also announced support for DNS over TLS in version 1.3.0.^[16]

Linux and Windows users can use DNS over TLS as a client through the NLnet Labs stubby daemon or Knot Resolver.^[17] Alternatively they may install getdns-utils^[18] to use DoT directly with the getdns_query tool. The unbound DNS resolver by NLnet Labs also supports DNS over TLS.^[19]

Apple's iOS 14 introduced OS-level support for DNS over TLS (and DNS over HTTPS). iOS does not allow manual configuration of DoT servers, and requires the use of a third-party application to make configuration changes.^[20]

systemd-resolved is a Linux-only implementation that can be configured to use DNS over TLS, by editing /etc/systemd/resolved.conf and enabling the setting DNSOverTLS.^[21][22] Most major Linux distributions have systemd installed by default.^{[23][circular reference]}

DNS over TLS was first implemented in a public recursive resolver by Quad9 in 2017.^[24][25] Other recursive resolver operators such as Google and Cloudflare followed suit in subsequent years, and now it is a broadly-supported feature generally available in most large recursive resolvers.^{[26][27][28][29][30][31][32][33][12]}

DoT can impede analysis and monitoring of DNS traffic for cybersecurity purposes. DoT has been used to bypass parental controls which operate at the (unencrypted) standard DNS level; Circle, a parental control router which relies on DNS queries to check domains against a blocklist, blocks DoT by default due to this.^[34] However, there are DNS providers that offer filtering and parental controls along with support for both DoT and DoH.^{[35][36][37][38][39][12]} In that scenario, DNS queries are checked against block lists once they are received by the provider rather than prior to leaving the user's router.

As with any communication, encryption of DNS requests by itself does not protect privacy. It protects against third-party observers, but does not guarantee what the endpoints do with the (then decrypted) data.

DoT clients do not necessarily directly query any authoritative name servers. The client may rely on the DoT server using traditional (port 53 or 853) queries to finally reach authoritative servers. Thus, DoT does not qualify as an end-to-end encrypted protocol, only hop-to-hop encrypted and only if DNS over TLS is used consistently.

DNS over HTTPS (DoH) is a similar protocol standard for encrypting DNS queries, differing only in the methods used for encryption and delivery from DoT. On the basis of privacy and security, whether or not a superior protocol exists among the two is a matter of controversial debate, while others argue the merits of either depend on the specific use case.^[40]

DNSCrypt is another network protocol that authenticates and encrypts DNS traffic, although it was never proposed to the Internet Engineering Task Force (IETF) with a Request for Comments (RFC).

• DNSCurve
• Public recursive name server
• DNS over HTTPS

• RFC 7858 – Specification for DNS over Transport Layer Security (TLS)
• RFC 8310 – Usage Profiles for DNS over TLS and DNS over DTLS
• DNS Privacy Project: dnsprivacy.org