hbonow.com DNSSEC Outage:
2015-03-09 - 2015-03-10
Updated: March 27, 2018
This page gives some details on the hbonow.com DNSSEC outage from March 9 to March 10, 2015. This outage occurred during the HBO Now product launch. Since Comcast is a competitor to HBO Now and one of the only ISPs supporting DNSSEC, a lot of people thought Comcast was intentionally blocking HBO Now, prompting complaints to the FCC.
Timeline / DNSViz
- 2015-03-09 21:21:37 UTC — Bogus DNSSEC delegation
- 2015-03-10 00:37:13 UTC — Bogus DNSSEC delegation
- 2015-03-10 01:04:41 UTC — Bogus DNSSEC delegation
- 2015-03-10 01:05:51 UTC — Bogus DNSSEC delegation
- 2015-03-10 01:48:14 UTC — Bogus DNSSEC delegation
- 2015-03-10 02:05:16 UTC — DNSSEC outage over
This DNSSEC outage was discussed on Hacker News.
The Internet Society admitted this DNSSEC outage.
- Thomas Ptacek:
"At the same time, once enrolled, the weird little pockets of the Internet that actually look for DNSSEC records when they do DNS lookups will instantly become susceptible to forgetting that your domain exists entirely if any misconfiguration occurs. That's not a hypothetical concern: the week HBO launched HBO Now, their cord-cutting all-online streaming service, it vanished for Comcast users whose DNS servers at the time enforced DNSSEC."
- Nicholas Weaver:
"If I was Comcast, after the HBO DNSSEC mess-up, on top of previous mess-ups where Comcast inevitably gets the blame, I'd be really really tempted to turn OFF DNSSEC validation. It has failed."