libsodium.org DNSSEC Outage: 2018-04-03
Updated: April 3, 2018
Overview
This page gives some details on the libsodium.org DNSSEC outage on April 3, 2018. This is at least the 5th DNSSEC outage for libsodium.org.
Timeline / DNSViz
- 2018-04-03 06:16:18 UTC — Bogus DNSSEC delegation
- 2018-04-03 06:16:42 UTC — Bogus DNSSEC delegation
- 2018-04-03 06:16:45 UTC — Bogus DNSSEC delegation
- 2018-04-03 06:17:53 UTC — Bogus DNSSEC delegation
- 2018-04-03 06:21:58 UTC — Bogus DNSSEC delegation
- 2018-04-03 09:06:50 UTC — last personally observed DNSSEC failure
- 2018-04-03 13:43:09 UTC — DNSSEC is unsigned
DNSSEC Debugger
Unlike DNSViz, Verisign's DNSSEC Debugger doesn't archive results, so here's a screenshot of my web browser's output from April 3, 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 libsodium.org. @8.8.8.8
; <<>> DiG 9.4.2-P2 <<>> +dnssec a libsodium.org. @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 24967
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 512
;; QUESTION SECTION:
;libsodium.org. IN A
;; Query time: 147 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Apr 3 06:16:14 2018
;; MSG SIZE rcvd: 42
You have to disable DNSSEC to make DNS queries work:
$ dig +cd a libsodium.org. @8.8.8.8
; <<>> DiG 9.4.2-P2 <<>> +cd a libsodium.org. @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59520
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;libsodium.org. IN A
;; ANSWER SECTION:
libsodium.org. 9999 IN A 37.59.238.213
;; Query time: 147 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Apr 3 06:16:14 2018
;; MSG SIZE rcvd: 47
Zonemaster
- zonemaster.net archived "Delegation from parent to child is not properly signed (no_dnskey)."
- zonemaster.fr archived "Delegation from parent to child is not properly signed (no_dnskey)."
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). Note the DS at .org, but "no chain to a trusted key or ds record." See DNSViz for a graphical representation.
[T] libsodium.org. 86400 IN DS 33101 13 2 b37674f220b87eeda8cb124fb84315b37c6fdcd2931547e20aa8bedce455195a
;; Domain: libsodium.org.
;; Signature ok but no chain to a trusted key or ds record
[S] libsodium.org. 86400 IN DNSKEY 256 3 13 ;{id = 53970 (zsk), size = 256b}
libsodium.org. 86400 IN DNSKEY 257 3 13 ;{id = 52433 (ksk), size = 256b}
[S] libsodium.org. 10000 IN A 37.59.238.213
;;[S] self sig OK; [B] bogus; [T] trusted
Logfile examples
- [1522736172] unbound[9744:0] info: validation failure <libsodium.org. A IN>: no keys have a DS with algorithm ECDSAP256SHA256 from 37.59.238.213 for key libsodium.org. while building chain of trust
- [1522746410] unbound[9744:0] info: validation failure <www.libsodium.org. A IN>: no keys have a DS with algorithm ECDSAP256SHA256 from 78.194.219.1 for key libsodium.org. while building chain of trust