.bw TLD DNSSEC Outage: 2016-11-21 to 2016-11-23

Updated: November 23, 2016

Overview

This page gives some details on the bw TLD DNSSEC outage from November 21 to November 23, 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 November 22, 2015:

November 21 2016 .bw (Botswana) 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 bw TLD during this outage.

With OpenDNS, which doesn't support DNSSEC, queries succeed:

$ dig google.co.bw. @resolver1.opendns.com.

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

;; QUESTION SECTION:
;google.co.bw. IN A

;; ANSWER SECTION:
google.co.bw. 300 IN A 216.58.192.227

;; Query time: 25 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Tue Nov 22 02:57:55 2016
;; MSG SIZE rcvd: 46


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

$ dig +dnssec google.co.bw. @8.8.8.8

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

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

;; Query time: 42 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 22 02:59:01 2016
;; MSG SIZE rcvd: 41

DNSCheck

Zonemaster

Logfile examples