usfj.mil DNSSEC Outage: 2015-06-10

Updated: June 11, 2015

Overview

This page gives some details on the usfj.mil DNSSEC outage from June 10 to June 11, 2015.

Timeline / DNSViz

OpenDNS and Google Public DNS

OpenDNS does not support DNSSEC, instead supporting DNSCurve. Among other advantages, DNSCurve is immune to DNSSEC outages. Google Public DNS currently supports only DNSSEC, and thus, Google's users saw SERVFAIL for queries under usfj.mil during this outage.

With OpenDNS, queries succeed:

$ dig mx usfj.mil. @resolver1.opendns.com.

; <<>> DiG 9.4.2-P2 <<>> mx usfj.mil. @resolver1.opendns.com.
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28256
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;usfj.mil. IN MX

;; AUTHORITY SECTION:
usfj.mil. 3600 IN SOA dns01.usfj.mil. postmaster.usfj.mil. 2015061101 28800 7200 3600000 7200

;; Query time: 151 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Thu Jun 11 00:26:30 2015
;; MSG SIZE rcvd: 95

With Google Public DNS, with DNSSEC, queries fail:

$ dig mx usfj.mil. @8.8.8.8

; <<>> DiG 9.4.2-P2 <<>> mx usfj.mil. @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 13487
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;usfj.mil. IN MX

;; Query time: 341 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Jun 11 00:26:12 2015
;; MSG SIZE rcvd: 26

Logfile examples