DNSSEC Resolver Test

This test determines whether your DNS resolver validates DNSSEC signatures. For this test you need JavaScript turned on.

Start test

DNSSEC for Users

Modern operating systems support DNSSEC validation out of the box—though not all of them. The alternative is to use a validating resolver in your local network, e.g. a home router with DNSSEC support.

If you'd like to experiment with a validating resolver on your computer, you may want to try Dnssec-Trigger (more information). Keep in mind that web browsers do not distinguish between DNSSEC validation failures and general DNS failures (there is no security warning like with HTTPS errors).

To re-run the above test, you also need to:

• Flush the DNS cache of your OS (Windows: ipconfig /flushdns)
• Restart browser or clear browser cache

DNSSEC for DNS Cache Operators

Modern operating systems ship the recursive DNS cache server with DNSSEC enabled in the default configuration. If this is not the case for you, follow the steps listed below for BIND or Unbound.

BIND

Since BIND 9.8, you can activate DNSSEC validation with the following lines in the options section of your named.conf:

• dnssec-enable yes;
• dnssec-validation auto;

Reload config: rndc reload

If you're running an older BIND version, you should update.

Unbound

Unbound ships with a tool for secure retrieval of the root KSK.

1. Update the root KSK: unbound-anchor
2. Make sure your unbound.conf contains the option auto-trust-anchor-file, e.g.: auto-trust-anchor-file "/var/lib/unbound/root.key"

Reload config: unbound-control reload

Test validation

• dig sigok.verteiltesysteme.net @127.0.0.1 (should return A record)
• dig sigfail.verteiltesysteme.net @127.0.0.1 (should return SERVFAIL)

If DNSSEC validation does not seem to work, check whether you're using more than one DNS resolver and whether each of them has DNSSEC validation enabled. The most common configuration error is to use a secondary DNS resolver without DNSSEC validation. Upon validation error, the operating system will fall back to the secondary resolver and the security checks of the primary resolver will be moot.

Results

• [2013-03-19] Presentation (HTML5), PDF (2.3 MB), Passive and Active Measurement Conference (PAM), Hong Kong.
• [2012-12-17] Paper (PDF), published in the Proceedings of the 2013 Passive and Active Measurement Conference (PAM).
• [2012-10-14] Presentation (HTML5), PDF (1.4 MB), DNS-OARC Workshop, Toronto.

Export SVG

Map shows ratio of validating clients per country, collected from October 2014 to March 2015. Some older result sets of the measurement (anonymized) are available for public download.

Other Tests

These tests use slightly different mechanics. Most users should get the same result on all tests, but in some cases there may be discrepancies. Discrepancies are usually caused by using a combination of validating and non-validating resolvers.

• www.dnssec-or-not.com: online test by VeriSign (no JavaScript required)
• internet.nl/connection: online test by Dutch Internet Standards Platform
• www.dnssec-failed.org: webpage with bogus signature by Comcast (will not open at all if you are using DNSSEC)

Acknowledgements

Thanks to A.G., Michael, Brody, Jean-Michel, Jan-Piet, Zekah and Stefan for providing valuable feedback.

Contact

Matthäus Wander <mail(at)wander.science>