.kg TLD DNSSEC Outage: 2022-08-18
Date: August 18, 2022
Overview
This page gives some details on the kg (Kyrgyzstan) TLD DNSSEC outage on August 18, 2022.
Timeline / DNSViz
- 2022-08-18 19:45:26 UTC — Bogus DNSSEC delegation
- 2022-08-18 19:45:40 UTC — Bogus DNSSEC delegation
- 2022-08-18 19:50:48 UTC — Bogus DNSSEC delegation
Verisign's DNSSEC Debugger
Here's a screenshot I took on August 18, 2022, of the DNSSEC Debugger output:
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 ns kg. @8.8.8.8.
; <<>> DiG 9.11.5-P4-5.1+deb10u7-Debian <<>> +dnssec ns kg. @8.8.8.8.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 7100
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 512
;; QUESTION SECTION:
;kg. IN NS
;; Query time: 219 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Aug 18 15:45:27 EDT 2022
;; MSG SIZE rcvd: 31
You have to disable DNSSEC to make DNS queries work:
$ dig +cd ns kg. @8.8.8.8.
; <<>> DiG 9.11.5-P4-5.1+deb10u7-Debian <<>> +cd ns kg. @8.8.8.8.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16673
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;kg. IN NS
;; ANSWER SECTION:
kg. 21600 IN NS KG.CCTLD.AUTHDNS.RIPE.NET.
kg. 21600 IN NS NS2.kg.
kg. 21600 IN NS NS.kg.
;; Query time: 133 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Aug 18 15:45:27 EDT 2022
;; MSG SIZE rcvd: 105
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):
[T] kg. 86400 IN DS 49954 5 1 285c47ca00e9416e0c6bd6f7317bf57b0ee1cc7d
kg. 86400 IN DS 49954 5 2 9166ca43b29f27bc7cc8b758f7027724ea2b860dbe49cf08a2763ea0e95e8754
;; Domain: kg.
;; Signature ok but no chain to a trusted key or ds record
[S] kg. 1800 IN DNSKEY 256 3 8 ;{id = 3529 (zsk), size = 2048b}
kg. 1800 IN DNSKEY 257 3 8 ;{id = 45982 (ksk), size = 2048b}
[S] Existence denied: kg. A
;;[S] self sig OK; [B] bogus; [T] trusted
Logfile examples
The below log entries come from 2 different Unbound instances running on different servers running different operating systems in different geographic locations.
- [1660851874] unbound[46624:0] info: validation failure <kg. NS IN>: no keys have a DS with algorithm RSASHA1 from 195.38.160.36 for key kg. while building chain of trust
- [1660851923] unbound[467:0] info: validation failure <kg. NS IN>: no keys have a DS with algorithm RSASHA1 from 195.38.160.38 for key kg. while building chain of trust
- [1660851940] unbound[46624:0] info: validation failure <kg. NS IN>: no keys have a DS with algorithm RSASHA1 from 193.0.9.84 for key kg. while building chain of trust
- [1660852222] unbound[467:0] info: validation failure <kg. NS IN>: no keys have a DS with algorithm RSASHA1 from 193.0.9.84 for key kg. while building chain of trust
- [1660852206] unbound[46624:0] info: validation failure <kg. NS IN>: no keys have a DS with algorithm RSASHA1 from 195.38.160.36 for key kg. while building chain of trust