.zm (Zambia) DNSSEC Outage: 2018-10-14 to 2018-10-15
Updated: October 15, 2018
Overview
This page gives some details on the .zm TLD DNSSEC outage from October 14 to October 15, 2018.
DNSViz / Timeline
- 2018-10-14 12:08:34 UTC — RRSIGs expire
- 2018-10-14 12:10:34 UTC — expired RRSIGs
- 2018-10-14 12:11:12 UTC — expired RRSIGs
- 2018-10-14 12:11:30 UTC — expired RRSIGs
- 2018-10-14 17:25:31 UTC — expired RRSIGs
- 2018-10-15 01:14:21 UTC — expired RRSIGs
- 2018-10-15 08:35:54 UTC — no RRSIGs
- 2018-10-15 14:46:39 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 October 14, 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 DNS SEC. With DNSSEC, DNS queries result in SERVFAIL:
$ dig +dnssec ns zm. @8.8.8.8
; <<>> DiG 9.4.2-P2 <<>> +dnssec ns zm. @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 49596
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 512
;; QUESTION SECTION:
;zm. IN NS
;; Query time: 315 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sun Oct 14 12:11:13 2018
;; MSG SIZE rcvd: 31
You have to disable DNSSEC to make DNS queries work:
$ dig +cd ns zm. @8.8.8.8
; <<>> DiG 9.4.2-P2 <<>> +cd ns zm. @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23692
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;zm. IN NS
;; ANSWER SECTION:
zm. 21599 IN NS ns-zm.afrinic.net.
zm. 21599 IN NS ns2.zamnet.zm.
zm. 21599 IN NS pch.nic.zm.
zm. 21599 IN NS ns1.zamnet.zm.
;; Query time: 31 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sun Oct 14 12:11:13 2018
;; MSG SIZE rcvd: 116
Zonemaster
Among other errors, zonemaster.iis.se archived "RRSIG with keytag 32227 and covering type(s) DNSKEY has already expired (expiration is: 1539518914)."
drill trace
Since DNSSEC contains so much garbage, I put the complete drill trace into its own fil e with the relevant portion below (emphasis added):
;; Domain: zm. [B] zm. 3600 IN DNSKEY 256 3 8 ;{id = 65488 (zsk), size = 1024b} zm. 3600 IN DNSKEY 257 3 8 ;{id = 32227 (ksk), size = 2048b} [B] Error verifying denial of existence for zm. type A: No keys with the keytag and algorithm from the RRSIG found ;;[S] self sig OK; [B] bogus; [T] trusted
Logfile examples
- [1539519071] unbound[26370:0] info: validation failure <zm. NS IN>: signature expired from 204.61.216.73 for key zm. while building chain of trust
- [1539538268] unbound[26370:0] info: validation failure <dnssec.zm. CAA IN>: signature expired from 196.216.168.44 for key zm. while building chain of trust
- [1539585695] unbound[26370:0] info: validation failure <zm. NS IN>: No DNSKEY record from 204.61.216.73 for key zm. while building chain of trust
- [1539614799] unbound[26370:0] info: validation failure <zm. NS IN>: No DNSKEY record from 204.61.216.73 for key zm. while building chain of trust