Experimental DNS Privacy Recursive Servers
The following servers are configured to support TLS on port 853 for testing purposes.
Live monitoring of these servers can be found on the Test Server Monitoring page.
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.
Note that the Yeti servers use a different root key for DNSSEC! See the Yeti project for more details
It is also known that Quad9 provide service on port 853 for DNS-over-TLS however this is not officially mentioned on their website.
|Hosted by||IP addresses||TLS Ports||Hostname for TLS|
|Base 64 encoded form of SPKI pin(s) for TLS |
|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.|
|Traffic volume only||HAProxy + BIND|
|Traffic volume only||Nginx + BIND|
|Traffic volume only||Unbound|
|2) Other servers with no/minimal logging|
|Quad9||220.127.116.11||853||dns.quad9.net||See https://quad9.net for details of privacy and filtering policies and alternative addresses(1). UDP and TCP service are also available on this address.|
|wikE3jYAA6jQmXYTr/rbHeEPmC78dQwZbQp6WdrseEs=||Traffic volume only||See https://blog.uncensoreddns.org/|
|853||dnsovertls2.sinodun.com||NAXBESvpjZMnPWQcrxa2KFIkHV/pDEIjRkA3hLWogSg=||Traffic volume only||Knot Resolver||Has some issues with DNSSEC responses - this is under investigation. Temporarily turned on verbose logs to debug.|
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.
|dns1.darkmoon.is||18.104.22.168||853||dns1.darkmoon.is||8sx8niFUiJvMM3C1qLE9cH79TuQQztzMVDtbKjpD/IQ=||Traffic volume only||Unbound|
UPDATED on 2nd Nov 2017
3) Servers with some logging, self-signed certs or no support for Strict mode
|Lorraine Data Network|
|Yes, logging at stunnel(2)||stunnel 4 + BIND|
Yes, for research purposes
Self-signed certificate, please 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 an IPv6 address or an SPKI pinset.
(2) Since the nameserver is behind a proxy the client IP is not logged inside the nameserver