The following servers are configured to support TLS on port 853 for testing purposes.
Note that they are experimental offerings with no guarantees on the lifetime of the service, service level provided. The level of logging may also vary (see the individual websites where available) - the information here about logging has not been verified.
Also note that the single SPKI pins published here for many of these servers are subject to change (e.g on Certificate renewal) and should be used with care!!
A YAML configuration file for Stubby containing a the details of these servers is provided with Stubby and can be found here. This file enables only the subset of servers operated by the stubby/getdns developers by default, users can choose to enable any of the other servers by uncommenting the relevant section (occasionally the file lags this page).
**Note that the Yeti servers use a different root key for DNSSEC! See the Yeti project for more details
|Hosted by||IP addresses||TLS Ports||Hostname for TLS|
|Base 64 encoded form of SPKI pin(s) for TLS |
|TLSA record published||Logging||Software||Notes|
|1) The following are currently enabled in the default Stubby config file because they are run by the stubby/getdns developers and have no known issues.|
|Y||Traffic volume only||HAProxy + BIND 9.12|
|Y||Traffic volume only||Nginx + BIND 9.12|
|Y||Traffic volume only||Unbound|
|2) Anycast services (with no/minimal logging)|
|853||dns.quad9.net||Quad9 do NOT publish or recommend use of SPKI pins with their servers.|
See https://quad9.net and their FAQ for details of privacy, logging and filtering policies on the main and alternative addresses(1). UDP and TCP service are also available on these addresses.
188.8.131.52 or 184.108.40.206
|853||cloudflare-dns.com||Cloudflare do NOT publish or recommend use of SPKI pins with their servers.|
UDP and TCP service are also available on these addresses. DNS-over-HTTPS is also available!
NOTE: To use this service by name only (i.e resolve the IP from the name) use 1dot1dot1dot1.cloudflare-dns.com.
|3) Other servers with no/minimal logging|
|wikE3jYAA6jQmXYTr/rbHeEPmC78dQwZbQp6WdrseEs=||Y||Traffic volume only||See https://blog.uncensoreddns.org/|
|Y||Traffic volume only||HAProxy + BIND 9.12||Supports TLS 1.3 and TLS 1.2. We think our stability problems are solved... see here for details. NOTE: This is using OpenSSL |
|853||dnsovertls2.sinodun.com||NAXBESvpjZMnPWQcrxa2KFIkHV/pDEIjRkA3hLWogSg=||Y||Traffic volume only||Knot Resolver||Has some issues with DNSSEC responses - this is under investigation.|
See https://dns.cmrg.net/ Note that on port 443 this server can serve both HTTP 1.1 traffic (to securely access the nameserver credentials) on TLS connections and DNS-over-TLS on separate TLS connections due to some nifty, experimental demultiplexing of traffic, described here.
Has some issues with DNSSEC responses - this is under investigation.
dns.larsdebruin.net (Previously dns1.darkmoon.is)
UPDATED on 30 Jan 2018
UPDATED on 30 Jan 2018 AAT+rHoKx5wQkWhxlfrIybFocBu3RBrPD2/ySwIwmvA=
|Traffic volume only||Unbound|
|None||HaProxy + Bind|
UPDATED 2nd May 2018:
THIS SERVER WILL BE RETIRED IN THE VERY NEAR FUTURE. USE dot.secure.eu INSTEAD!!
NOTE: SecureDNS has support for additional TLDs of OpenNIC, Emercoin, and Namecoin
|853||dot.securedns.eu||h3mufC43MEqRD6uE4lz6gAgULZ5/riqH/E+U+jE3H8g=||None||HaProxy + Bind|
NOTE 1: SecureDNS has support for additional TLDs of OpenNIC, Emercoin, and Namecoin
NOTE 2: While both secure.eu and dot.secure.eu are running pin only validation for dot.secure.eu will not work!
|dns.bitgeek.in (India)||220.127.116.11||853||dns.bitgeek.in||FndaG4ezEBQs4k0Ya3xt3z4BjFEyQHd7B75nRyP1nTs=||Traffic volume only||Nginx + BIND|
|Lorraine Data Network|
|Traffic volume only||stunnel 4 + BIND|
See https://ldn-fai.net/serveur-dns-recursif-ouvert/ (note, logging of IP address at stunnel no longer performed).
|dns.neutopia.org||wTeXHM8aczvhRSi0cv2qOXkXInoDU+2C+M8MpRyT3OI=||No logging||Knot resolver|
4) Servers with some logging, self-signed certs or no support for Strict mode
Yes, for research purposes
Self-signed certificate, use SPKI pinning.
UPDATED on 26th Jun 2017
|Yes, see Yeti website||Unbound||See https://dns-resolver.yeti.eu.org/|
|Yes, see OARC website||Unbound|
See OARC website NOTE: As of June 2017 this server does not support Strict Mode because it does not offer the correct cipher suites to match RFC7525 recommendations.
(1) More details of the service are available in various blogs e.g. see Stephane Bortzmeyer's blog. Note that Quad9 have not announced a SPKI pinset.