mm TLD DNSSEC Outage: 2016-06-29 to 2016-06-30

Updated: June 30, 2016

Overview

This page gives some details on the .mm (Myanmar) DNSSEC outage from June 29 to June 30, 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 June 29, 2016:

June 29, 2016 mm 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 .mm during this outage.

$ dig google.com.mm. @resolver1.opendns.com.

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

;; QUESTION SECTION:
;google.com.mm. IN A

;; ANSWER SECTION:
google.com.mm. 300 IN A 216.58.192.196

;; Query time: 391 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Wed Jun 29 13:10:31 2016
;; MSG SIZE rcvd: 47

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

$ dig +dnssec google.com.mm. @8.8.8.8

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 512
;; QUESTION SECTION:
;google.com.mm. IN A

;; Query time: 1000 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Jun 29 13:10:32 2016
;; MSG SIZE rcvd: 42

dnscheck

dnscheck.labs.nic.cz shows expired RRSIGs (requires javascript).

dnscheck.iis.se shows expired RRSIGs (requires javascript).

Zonemaster

zonemaster.net archived expired RRSIGs.

zonemaster.fr archived expired RRSIGs.

Logfile examples