DNS over TLS

From Wikipedia, the free encyclopedia
DNS over TLS
StatusProposed Standard
Latest versionRFC 7858, RFC 8310
May 2016 and March 2018

DNS over TLS (DoT) is a network security protocol for encrypting and wrapping Domain Name System (DNS) queries and answers via the Transport Layer Security (TLS) protocol. The goal of the method is to increase user privacy and security by preventing eavesdropping and manipulation of DNS data via man-in-the-middle attacks. The well-known port number for DoT is 853.

While DNS over TLS is applicable to any DNS transaction, it was first standardized for use between stub or forwarding resolvers and recursive resolvers, in RFC 7858 in May of 2016. Subsequent IETF efforts specify the use of DoT between recursive and authoritative servers ("Authoritative DNS over TLS" or "ADoT")[1] and a related implementation between authoritative servers (Zone Transfer-over-TLS or "xfr-over-TLS").[2]

Server software[edit]

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]

Client software[edit]

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

In April 2018, Google announced that Android Pie will include support for DNS over TLS,[14] 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.[15]

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

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.[19]

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.[20][21] Most major Linux distributions have systemd installed by default.[22][circular reference]

Public resolvers[edit]

DNS over TLS was first implemented in a public recursive resolver by Quad9 in 2017.[23][24] 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.[25][26][27][28][29][30][31][32]

Criticisms and implementation considerations[edit]

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.[33] However, there are DNS providers that offer filtering and parental controls along with support for both DoT and DoH.[34][35][36][37][38] 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.[39]

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).

See also[edit]


  1. ^ Henderson, Karl; April, Tim; Livingood, Jason (2020-02-14). "Authoritative DNS-over-TLS Operational Considerations". Ietf Datatracker. Internet Engineering Task Force. Retrieved 17 July 2021.
  2. ^ Mankin, Allison (2019-07-08). "DNS Zone Transfer-over-TLS". Ietf Datatracker. Internet Engineering Task Force. Retrieved 17 July 2021.
  3. ^ "4. BIND 9 Configuration Reference — BIND 9 documentation". bind9.readthedocs.io. Retrieved 2021-11-14.
  4. ^ "Bind - DNS over TLS".
  5. ^ "Unbound version 1.7.3 Changelog". Archived from the original on 2018-08-07. Retrieved 2018-08-07.
  6. ^ Aleksandersen, Daniel. "Actually secure DNS over TLS in Unbound". Ctrl blog. Retrieved 2018-08-07.
  7. ^ "openbsd-cvs mailing list archives".
  8. ^ "openbsd-cvs mailing list archives".
  9. ^ "blockerDNS - Block Ads and Online Trackers So You Can Browse the Web Privately on Your Android Phone Without Installing an App!". blockerdns.com. Retrieved 2019-08-14.
  10. ^ "The official release of AdGuard DNS — a new unique approach to privacy-oriented DNS". AdGuard Blog. Retrieved 2019-08-14.
  11. ^ "Blahdns -- Dns service support DoH, DoT, DNSCrypt". blahdns.com. Retrieved 2019-08-14.
  12. ^ "DNS over TLS support in Android P Developer Preview". Android Developers Blog. Retrieved 2019-12-07.
  13. ^ Wallen, Jack (August 23, 2018). "How to enable DNS over TLS in Android Pie". TechRepublic. Retrieved 2021-03-17.
  14. ^ "DNS over TLS support in Android P Developer Preview". Google Security Blog. April 17, 2018.
  15. ^ "DNS-over-TLS". dnsdist.org. Retrieved 25 April 2018.
  16. ^ "Knot Resolver".
  17. ^ Package: getdns-utils, retrieved 2019-04-04
  18. ^ "Unbound - About". NLnet Labs. Retrieved 2020-05-26.
  19. ^ Cimpanu, Catalin. "Apple adds support for encrypted DNS (DoH and DoT)". ZDNet. Retrieved 2020-10-03.
  20. ^ "resolved.conf manual page". Retrieved 16 December 2019.
  21. ^ "Fedora Magazine: Use DNS over TLS". 10 July 2020. Retrieved 4 September 2020.
  22. ^ "Systemd adoption". Retrieved 16 December 2019.
  23. ^ Band, Alex (2017-11-20). "Privacy: Using DNS-over-TLS with the Quad9 DNS Service". Medium. Retrieved 17 July 2021. Recently the Quad9 DNS service was launched. Quad9 differentiates from similar services by focusing on security and privacy. One interesting feature is the fact that you can communicate with the service using DNS-over-TLS. This encrypts the communication between your client and the DNS server, safeguarding your privacy.
  24. ^ Bortzmeyer, Stéphane (2017-11-21). "Quad9 is a public DNS resolver, with promises of better privacy, and a DNS-over-TLS access". RIPE Labs. Retrieved 17 July 2021. Last week, the new DNS resolver Quad9 has been announced. It is a public DNS resolver with the additional benefit that it is accessible in a secure way over TLS (RFC 7858). There are plenty of public DNS resolvers, but the link to them is not secure. This allows hijackings, as seen in Turkey, as well as third-party monitoring. The new Quad9 service on the other hand is operated by the not-for-profit Packet Clearing House (PCH), which manages large parts of the DNS infrastructure, and it allows access to the DNS over TLS. This makes it very difficult for third parties to listen in. And it makes it possible to authenticate the resolver.
  25. ^ "Public DNS resolver Anycast DNS for All". www.dnslify.com. Retrieved 2020-05-26.
  26. ^ "Telsy TRT". Archived from the original on 2021-01-31. Retrieved 2020-05-26.
  27. ^ "How to keep your ISP's nose out of your browser history with encrypted DNS". Ars Technica. Retrieved 2018-04-08.
  28. ^ "DNS over TLS - Cloudflare Resolver". developers.cloudflare.com. Retrieved 2018-04-08.
  29. ^ "Google Public DNS now supports DNS-over-TLS". Google Online Security Blog. Retrieved 2019-01-10.
  30. ^ "Quad9, a Public DNS Resolver - with Security". RIPE Labs. 21 November 2017. Retrieved 2018-04-08.
  31. ^ "Troubleshooting DNS over TLS". 13 May 2018.[user-generated source]
  32. ^ "LibreDNS". LibreDNS. Retrieved 2019-10-20.
  33. ^ "Managing encrypted DNS connections (DNS over TLS, DNS over HTTPS) with Circle". Circle Support Center. Archived from the original on 2020-08-03. Retrieved 2020-07-07.
  34. ^ Gallagher, Sean (16 November 2017). "New Quad9 DNS service blocks malicious domains for everyone". Ars Technica. Retrieved 14 November 2021. The system blocks domains associated with botnets, phishing attacks, and other malicious Internet hosts.
  35. ^ "Parental Control with DNS over TLS Support". CleanBrowsing. Retrieved 2020-08-20.
  36. ^ "Parental Control with DNS Over HTTPS (DoH) Support". CleanBrowsing. Retrieved 2020-08-20.
  37. ^ "Products". blockerdns.com. Retrieved 2020-08-20.
  38. ^ "Protect your privacy with DNS-over-TLS on SafeDNS". SafeDNS. Archived from the original on 2020-09-18. Retrieved 2020-08-20.
  39. ^ Claburn, Thomas (2020-05-20). "Google rolls out pro-privacy DNS-over-HTTPS support in Chrome 83... with a handy kill switch for corporate IT". The Register. Retrieved 2021-02-03.

External links[edit]