.by (Belarus) TLD DNSSEC Outage: 2018-11-23
Date: November 23, 2018
Overview
This page gives some details on the .by DNSSEC outage on November 23, 2018.
Timeline / DNSViz
- 2018-11-23 11:01:09 UTC — No RRSIGs
- 2018-11-23 11:01:34 UTC — No RRSIGs
- 2018-11-23 11:02:17 UTC — No RRSIGs
- 2018-11-23 11:57:21 UTC — last personally observed DNSSEC failure
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 23, 2018:
Google Public DNS: with and without DNSSEC
DNSSEC can be disabled in queries via the CD (checking disabled) bit. Let's compare DNS queries with and without DNSSEC. With DNSSEC, DNS queries result in SERVFAIL:
$ dig +dnssec ns by. @8.8.8.8
; <<>> DiG 9.4.2-P2 <<>> +dnssec ns by. @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 26488
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 512
;; QUESTION SECTION:
;by. IN NS
;; Query time: 78 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Nov 23 11:01:19 2018
;; MSG SIZE rcvd: 31
You have to disable DNSSEC to make DNS work:
$ dig +cd ns by. @8.8.8.8
; <<>> DiG 9.4.2-P2 <<>> +cd ns by. @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50957
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;by. IN NS
;; ANSWER SECTION:
by. 3599 IN NS dns4.tld.tutby.com.
by. 3599 IN NS dns1.tld.tutby.com.
by. 3599 IN NS dns5.tld.tutby.com.
by. 3599 IN NS dns3.tld.tutby.com.
by. 3599 IN NS dns2.tld.tutby.com.
;; Query time: 161 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Nov 23 11:01:19 2018
;; MSG SIZE rcvd: 128
drill trace
Since DNSSEC contains so much garbage, I put the complete drill trace into its own file with the relevant portion below (emphasis added):
;; Domain: by.
;; No DNSKEY record found for by.
[U] No data found for: by. type A
;;[S] self sig OK; [B] bogus; [T] trusted
Logfile examples
- [1542970879] unbound[86384:0] info: validation failure <by. NS IN>: no signatures from 93.125.30.44
- [1542971079] unbound[86384:0] info: validation failure <by. NS IN>: no signatures from 178.172.160.20
- [1542973312] unbound[12560:0] info: validation failure <dnssec.by. NS IN>: No DNSKEY record from 178.172.160.20 for key by. while building chain of trust
- [1542974241] unbound[86384:0] info: validation failure <by. NS IN>: No DNSKEY record from 195.209.35.70 for key by. while building chain of trust