bn TLD DNSSEC Outage: 2022-05-18 to 2022-05-19
Date: May 20, 2022
Overview
This page gives some details on the bn (Brunei) TLD DNSSEC outage from May 18 to May 19, 2022.
Verisign's DNSSEC Debugger
Verisign doesn't archive test results, unlike DNSViz. So here's a screenshot I took on May 18, 2022:
Timeline / DNSViz
- 2022-05-18 02:34:33 UTC — Expired RRSIGs
- 2022-05-18 07:10:27 UTC — Expired RRSIGs
- 2022-05-18 08:23:54 UTC — Expired RRSIGs
- 2022-05-18 10:47:08 UTC — Bogus DNSSEC delegation
- 2022-05-18 10:47:55 UTC — Bogus DNSSEC delegation
- 2022-05-18 10:57:39 UTC — Expired RRSIGs
- 2022-05-18 12:53:04 UTC — Bogus DNSSEC delegation
- 2022-05-18 14:17:58 UTC — Bogus DNSSEC delegation
- 2022-05-18 18:40:07 UTC — Bogus DNSSEC delegation
- 2022-05-18 23:37:56 UTC — Bogus DNSSEC delegation
- 2022-05-19 00:59:38 UTC — Bogus DNSSEC delegation
- 2022-05-19 06:27:59 UTC — Bogus DNSSEC delegation
- 2022-05-19 07:53:44 UTC — Bogus DNSSEC delegation
- 2022-05-19 10:16:41 UTC — Bogus DNSSEC delegation
- 2022-05-19 18:14:41 UTC — Bogus DNSSEC delegation
- 2022-05-19 20:40:26 UTC — Bogus DNSSEC delegation
- 2022-05-19 20:42:34 UTC — Bogus DNSSEC delegation
- 2022-05-19 20:50:42 UTC — Bogus DNSSEC delegation
- 2022-05-19 21:09:01 UTC — Bogus bn/SOA
- 2022-05-19 21:14:07 UTC — last personally observed bn DNSSEC failure
Here's a screenshot example:
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 bn. @8.8.8.8.
; <<>> dig 9.10.8-P1 <<>> +dnssec ns bn. @8.8.8.8.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 2502
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 512
;; QUESTION SECTION:
;bn. IN NS
;; Query time: 347 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed May 18 10:51:07 UTC 2022
;; MSG SIZE rcvd: 31
You have to disable DNSSEC to make DNS work:
$ dig +cd ns bn. @8.8.8.8.
; <<>> dig 9.10.8-P1 <<>> +cd ns bn. @8.8.8.8.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25256
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;bn. IN NS
;; ANSWER SECTION:
bn. 3600 IN NS NS1.BNNIC.bn.
bn. 3600 IN NS NS4.APNIC.NET.
bn. 3600 IN NS NS2.BNNIC.bn.
bn. 3600 IN NS BN-NS.ANYCAST.PCH.NET.
;; Query time: 96 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed May 18 10:51:07 UTC 2022
;; MSG SIZE rcvd: 132
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):
[T] bn. 86400 IN DS 26224 8 2 eab03d1aa2537fc2222def6383be358b88d50520f530d1f1cc4f40f1d83e4109
;; Domain: bn.
;; Signature ok but no chain to a trusted key or ds record
[S] bn. 3600 IN DNSKEY 256 3 8 ;{id = 6468 (zsk), size = 2048b}
bn. 3600 IN DNSKEY 256 3 8 ;{id = 31740 (zsk), size = 2048b}
bn. 3600 IN DNSKEY 256 3 8 ;{id = 62205 (zsk), size = 2048b}
bn. 3600 IN DNSKEY 257 3 8 ;{id = 42604 (ksk), size = 2048b}
[S] Existence denied: bn. A
;;[S] self sig OK; [B] bogus; [T] trusted; [U] unsigned
Zonemaster
- zonemaster.net saw this DNSSEC outage (archive.ph snapshot)
- zonemaster.iis.se also saw this DNSSEC outage (archive.ph snapshot)
dns.google.com
Here's a screenshot from dns.google.com during this DNSSEC outage:
And here's an archive.ph snapshot showing the same.
Logfile examples
- [1652871065] unbound[71336:0] info: validation failure <bn. NS IN>: no keys have a DS with algorithm RSASHA256 from 194.0.1.33 for key bn. while building chain of trust
- [1652871218] unbound[71336:0] info: validation failure <bn. NS IN>: no keys have a DS with algorithm RSASHA256 from 204.61.216.87 for key bn. while building chain of trust
- [1652871530] unbound[71336:0] info: validation failure <bn. NS IN>: no keys have a DS with algorithm RSASHA256 from 202.12.31.53 for key bn. while building chain of trust
- [1652878061] unbound[71336:0] info: validation failure <bn. NS IN>: signature missing from 202.12.31.53 for key bn. while building chain of trust
- [1652878179] unbound[71336:0] info: validation failure <bn. NS IN>: signature missing from 204.61.216.87 for key bn. while building chain of trust
- [1652878719] unbound[71336:0] info: validation failure <bn. NS IN>: signature missing from 194.0.1.33 for key bn. while building chain of trus
- [1652912142] unbound[71336:0] info: validation failure <bn. NS IN>: signature missing from 202.12.31.53 for key bn. while building chain of trust
- [1652912265] unbound[71336:0] info: validation failure <bn. NS IN>: signature missing from 204.61.216.87 for key bn. while building chain of trust
- [1652912361] unbound[71336:0] info: validation failure <bn. NS IN>: signature missing from 194.0.1.33 for key bn. while building chain of trust
- [1652912453] unbound[71336:0] info: validation failure <bn. NS IN>: no keys have a DS with algorithm RSASHA256 from 202.12.31.53 for key bn. while building chain of trust
- [1652912550] unbound[71336:0] info: validation failure <bn. NS IN>: no keys have a DS with algorithm RSASHA256 from 204.61.216.87 for key bn. while building chain of trust
- [1652913226] unbound[71336:0] info: validation failure <bn. NS IN>: no keys have a DS with algorithm RSASHA256 from 194.0.1.33 for key bn. while building chain of trust
- [1652994546] unbound[71336:0] info: validation failure <bn. NS IN>: no keys have a DS with algorithm RSASHA256 from 204.61.216.87 for key bn. while building chain of trust
- [1652994636] unbound[71336:0] info: validation failure <bn. NS IN>: no keys have a DS with algorithm RSASHA256 from 202.12.31.53 for key bn. while building chain of trust
- [1652994847] unbound[71336:0] info: validation failure <bn. NS IN>: no keys have a DS with algorithm RSASHA256 from 202.12.31.53 for key bn. while building chain of trust