dnscrypt.pl DNSSEC Outage: 2017-06-11/13
Updated: June 15, 2017
Overview
This page gives some details on the dnscrypt.pl DNSSEC outage from June 11 to June 13, 2017. This site has had multiple DNSSEC outages.
Timeline / DNSViz
- 2017-06-11 21:27:29 UTC — RRSIGs expire
- 2017-06-11 21:28:10 UTC — expired RRSIGs
- 2017-06-11 21:30:57 UTC — expired RRSIGs
- 2017-06-11 21:31:22 UTC — expired RRSIGs
- 2017-06-11 21:33:45 UTC — expired RRSIGs
- 2017-06-11 21:36:12 UTC — expired RRSIGs
- 2017-06-12 03:32:07 UTC — expired RRSIGs
- 2017-06-12 09:58:53 UTC — expired RRSIGs
- 2017-06-12 17:59:00 UTC — expired RRSIGs
- 2017-06-13 01:58:21 UTC — expired RRSIGs
- 2017-06-13 09:58:54 UTC — expired RRSIGs
- 2017-06-13 17:58:38 UTC — DNSSEC outage over
DNSSEC Debugger
Unlike DNSViz, Verisign's DNSSEC Debugger doesn't archive results, so here's a screenshot of my web browser's output from June 12, 2017:

OpenDNS & Google Public DNS
OpenDNS does not support DNSSEC, and instead supports DNSCurve. Google Public DNS currently supports only DNSSEC, and thus, Google's users saw SERVFAIL for queries under dnscrypt.pl during this outage.
With OpenDNS, without DNSSEC, queries succeed:
$ dig dnscrypt.pl. @resolver1.opendns.com.
; <<>> DiG 9.4.2-P2 <<>> dnscrypt.pl. @resolver1.opendns.com.
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34238
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;dnscrypt.pl. IN A
;; ANSWER SECTION:
dnscrypt.pl. 86400 IN A 178.62.233.48
;; Query time: 174 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Sun Jun 11 21:33:38 2017
;; MSG SIZE rcvd: 45
With Google Public DNS, because of DNSSEC, queries fail:
$ dig +dnssec dnscrypt.pl. @8.8.8.8
; <<>> DiG 9.4.2-P2 <<>> +dnssec dnscrypt.pl. @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 22501
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 512
;; QUESTION SECTION:
;dnscrypt.pl. IN A
;; Query time: 336 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sun Jun 11 21:33:38 2017
;; MSG SIZE rcvd: 40
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: dnscrypt.pl.
[B] dnscrypt.pl. 86400 IN DNSKEY 256 3 5 ;{id = 1651 (zsk), size = 1024b}
dnscrypt.pl. 86400 IN DNSKEY 257 3 5 ;{id = 65416 (ksk), size = 2048b}
dnscrypt.pl. 86400 IN DNSKEY 256 3 13 ;{id = 55894 (zsk), size = 256b}
dnscrypt.pl. 86400 IN DNSKEY 256 3 7 ;{id = 1802 (zsk), size = 1024b}
dnscrypt.pl. 86400 IN DNSKEY 257 3 13 ;{id = 55059 (ksk), size = 256b}
dnscrypt.pl. 86400 IN DNSKEY 257 3 7 ;{id = 5991 (ksk), size = 2048b}
[B] dnscrypt.pl. 86400 IN A 178.62.233.48
;; Error: No keys with the keytag and algorithm from the RRSIG found
;;[S] self sig OK; [B] bogus; [T] trusted
dns.google.com
dns.google.com is related to but seperate from Google Public DNS. During this DNSSEC outage, dns.google.com showed the following for dnscrypt.pl:
Logfile examples
- [1497216596] unbound[61085:0] info: validation failure <www.dnscrypt.pl. A IN>: signature expired from 193.70.13.218 for key dnscrypt.pl. while building chain of trust
- [1497239098] unbound[61085:0] info: validation failure <dnscrypt.pl. MX IN>: signature expired from 193.70.13.218 for key dnscrypt.pl. while building chain of trust