libsodium.org DNSSEC Outage:
2018-03-04 to 2018-03-05
Updated: March 5, 2018
Overview
This page gives some details on the libsodium.org DNSSEC outage from March 4 to March 5, 2018. This is at least the 4th DNSSEC outage for libsodium.org.
Timeline / DNSViz
- 2018-03-04 21:41:37 UTC — RRSIGs expire
- 2018-03-04 21:43:54 UTC — expired RRSIGs
- 2018-03-05 03:19:29 UTC — expired RRSIGs
- 2018-03-05 12:12:10 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 March 5, 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 a download.libsodium.org. @8.8.8.8
; <<>> DiG 9.4.2-P2 <<>> +dnssec a download.libsodium.org. @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 12224
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 512
;; QUESTION SECTION:
;download.libsodium.org. IN A
;; Query time: 289 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Mar 5 03:48:31 2018
;; MSG SIZE rcvd: 51
You have to disable DNSSEC to make DNS queries work:
$ dig +cd a download.libsodium.org. @8.8.8.8
; <<>> DiG 9.4.2-P2 <<>> +cd a download.libsodium.org. @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22483
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;download.libsodium.org. IN A
;; ANSWER SECTION:
download.libsodium.org. 9999 IN A 37.59.238.213
;; Query time: 145 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Mar 5 03:48:31 2018
;; MSG SIZE rcvd: 56
Zonemaster
- zonemaster.net archived "Delegation from parent to child is not properly signed (signature: DNSSEC signature has expired)."
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: libsodium.org.
[B] libsodium.org. 86400 IN DNSKEY 256 3 13 ;{id = 26057 (zsk), size = 256b}
libsodium.org. 86400 IN DNSKEY 256 3 13 ;{id = 54527 (zsk), size = 256b}
libsodium.org. 86400 IN DNSKEY 256 3 13 ;{id = 31363 (zsk), size = 256b}
libsodium.org. 86400 IN DNSKEY 257 3 13 ;{id = 33101 (ksk), size = 256b}
[B] Error verifying denial of existence for download.libsodium.org. DS: No keys with the keytag and algorithm from the RRSIG found
;; No ds record for delegation
;; Domain: download.libsodium.org.
;; No DNSKEY record found for download.libsodium.org.
[B] download.libsodium.org. 10000 IN A 37.59.238.213
;; Error: No keys with the keytag and algorithm from the RRSIG found
;;[S] self sig OK; [B] bogus; [T] trusted
Logfile examples
- [1520199795] unbound[39485:0] info: validation failure <libsodium.org. A IN>: signature expired from 78.194.219.1 for key libsodium.org. while building chain of trust
- [1520200090] unbound[39485:0] info: validation failure <www.libsodium.org. A IN>: signature expired from 37.59.238.213 for key libsodium.org. while building chain of trust
- [1520221705] unbound[39485:0] info: validation failure <download.libsodium.org. A IN>: signature expired from 78.194.219.1 for key libsodium.org. while building chain of trust
- [1520251930] unbound[8805:0] info: validation failure <download.libsodium.org. A IN>: key for validation libsodium.org. is marked as invalid because of a previous validation failure <libsodium.org. A IN>: signature expired from 37.59.238.213 for key libsodium.org. while building chain of trust