.mm (Myanmar) DNSSEC Outage: 2016-03-02 to 2016-03-03

Updated: March 3, 2016

Overview

This page gives some details on the .mm (Myanmar) TLD DNSSEC outage from March 2 to March 3, 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 March 2, 2016: March 2, 2016 .mm (Myanmar) TLD 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.

With OpenDNS, queries succeed:

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

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

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

;; ANSWER SECTION:
www.google.com.mm. 300 IN A 216.58.216.227

;; Query time: 24 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Wed Mar 2 05:58:40 2016
;; MSG SIZE rcvd: 51

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

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

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

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

;; Query time: 765 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Mar 2 05:58:41 2016
;; MSG SIZE rcvd: 46

dnscheck

dnscheck.iis.se shows expired signatures at 2016-03-02 06:00:56 (requires javascript).

dnscheck.labs.nic.cz shows expired signatures at 2016-03-02 06:01:54 (requires javascript).

Zonemaster

Zonemaster archived this .mm TLD DNSSEC outage.

Logfile examples