lb (Lebanon) DNSSEC Outage: 2015-03-12

Updated: March 14, 2015

Overview

This page gives some details on the lb (Lebanon) DNSSEC outage on March 12, 2015. The outage lasted approximately 11 hours.

Timeline / DNSViz

Verisign's DNSSEC Debugger

Here's a screenshot I took on March 12, 2015, of the DNSSEC Debugger output:

lb DNSSEC outage 2015-03-12

OpenDNS vs. Google Public DNS

While Google Public DNS supports DNSSEC, OpenDNS supports the superior DNSCurve, which is (among other advantages) immune to DNSSEC failures. During this outage, Google failed to resolve names under lb while OpenDNS worked normally.

With OpenDNS, queries succeed:

$ dig www.google.com.lb @resolver1.opendns.com

; <<>> DiG 9.4.2-P2 <<>> www.google.com.lb @resolver1.opendns.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45044
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com.lb. IN A

;; ANSWER SECTION:
www.google.com.lb. 300 IN A 216.58.216.227

;; Query time: 29 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Thu Mar 12 16:46:28 2015
;; MSG SIZE rcvd: 51


With Google Public DNS, queries fail:

$ dig www.google.com.lb @8.8.8.8

; <<>> DiG 9.4.2-P2 <<>> www.google.com.lb @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 27176
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com.lb. IN A

;; Query time: 251 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Mar 12 16:46:22 2015
;; MSG SIZE rcvd: 35

dnscheck

dnscheck.iis.se archived a DNSSEC outage at 2015-03-12 11:10:15 (requires javascript).

dnscheck.labs.nic.cz archived a DNSSEC outage at 2015-03-12 11:11:04 (requires javascript).

Logfile examples