dnssec-tools.org DNSSEC Outage: 2016-10-24 to 2016-10-25

Updated: October 25, 2016

Overview

This page gives some details on the dnssec-tools.org DNSSEC outage from October 24 to October 25, 2016.

Timeline / DNSViz

DNSSEC Debugger

Unlike DNSViz, Verisign's DNSSEC Debugger doesn't archive results, so here's a screenshot of my web browser's output from October 24, 2016:

October 24, 2016 dnssec-tools.org DNSSEC outage

OpenDNS & Google Public DNS

OpenDNS does not support DNSSEC, instead supporting DNSCurve. Google Public DNS currently supports only DNSSEC, and thus, Google's users saw SERVFAIL for queries under dnssec-tools.org during this outage.

$ dig www.dnssec-tools.org @resolver1.opendns.com.

; <<>> DiG 9.4.2-P2 <<>> www.dnssec-tools.org @resolver1.opendns.com.
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2377
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.dnssec-tools.org. IN A

;; ANSWER SECTION:
www.dnssec-tools.org. 300 IN CNAME dnssec-tools.org.
dnssec-tools.org. 205 IN A 64.90.35.104

;; Query time: 24 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Mon Oct 24 22:04:22 2016
;; MSG SIZE rcvd: 68


With Google Public DNS, because of DNSSEC, queries fail:

$ dig +dnssec www.dnssec-tools.org @8.8.8.8

; <<>> DiG 9.4.2-P2 <<>> +dnssec www.dnssec-tools.org @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 10785
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 512
;; QUESTION SECTION:
;www.dnssec-tools.org. IN A

;; Query time: 218 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Oct 24 22:04:22 2016
;; MSG SIZE rcvd: 49

dnscheck

Zonemaster

Logfile examples