.firestone TLD DNSSEC Outage: 2019-08-07
Date: August 7, 2019
Overview
This page gives some details on the .firestone TLD DNSSEC on August 7.
Timeline / DNSViz
(At the time of this writing, DNSViz historical archives have been down for months. DNSSEC makes its users think downtime doesn't matter.)
- 2019-08-07 08:33:53 UTC — first personally observed .firestone DNSSEC failure, "no signatures"
- 2019-08-07 09:22:53 UTC — last personally observed .firestone DNSSEC failure, "no signatures"
DNSSEC Debugger
Verisign's DNSSEC Debugger doesn't archive results, so here's a screenshot of my web browser's output from August 7, 2019:
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: firestone.
[B] firestone. 86400 IN DNSKEY 256 3 8 ;{id = 43114 (zsk), size = 1024b}
firestone. 86400 IN DNSKEY 257 3 8 ;{id = 9944 (ksk), size = 2048b}
[U] No data found for: firestone. type A
;;[S] self sig OK; [B] bogus; [T] trusted
Google 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.
$ dig +dnssec ns firestone. @8.8.8.8
; <<>> DiG 9.4.2-P2 <<>> +dnssec ns firestone. @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 12664
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 512
;; QUESTION SECTION:
;firestone. IN NS
;; Query time: 49 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Aug 7 08:33:53 2019
;; MSG SIZE rcvd: 38
$ dig +cd ns firestone. @8.8.8.8
; <<>> DiG 9.4.2-P2 <<>> +cd ns firestone. @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49470
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;firestone. IN NS
;; ANSWER SECTION:
firestone. 21599 IN NS a.gmoregistry.net.
firestone. 21599 IN NS l.gmoregistry.net.
firestone. 21599 IN NS k.gmoregistry.net.
firestone. 21599 IN NS b.gmoregistry.net.
;; Query time: 28 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Aug 7 08:33:54 2019
;; MSG SIZE rcvd: 106
Logfile examples
These Unbound log entries come from different Unbound instances, each on different servers in different geographical regions.
- [1565166833] unbound[78783:0] info: validation failure <firestone. NS IN>: no signatures from 37.209.194.4
- [1565167028] unbound[78783:0] info: validation failure <firestone. NS IN>: no signatures from 37.209.194.4
- [1565167261] unbound[78783:0] info: validation failure <firestone. NS IN>: no signatures from 37.209.194.4 for key firestone. while building chain of trust
- [1565168142] unbound[177:0] info: validation failure <firestone. NS IN>: no signatures from 37.209.192.4 for key firestone. while building chain of trust
- [1565169773] unbound[78783:0] info: validation failure <firestone. NS IN>: no signatures from 37.209.192.4 for key firestone. while building chain of trust