slack.com DNSSEC Outage: 2021-09-30

Date: September 30, 2021

Overview

This page gives some details on the slack.com partial DNSSEC outage on September 30, 2021.

dns-operations

• [dns-operations] slack.com bogus
• archive.is copy
• archive.org copy

outages list

• outages] Fwd: [dns-operations] slack.com bogus
• archive.is copy
• archive.org copy

NANOG

• slack.com
• archive.is copy
• archive.org copy

status.slack.com

• Thursday September 30, 2021
• archive.is copy
• archive.org copy

Slack blog

Slack acknowledged this DNSSEC outage on their blog, noting it was a partial outage that lasted 24 hours and that it "was the third unsuccessful attempt to enable DNSSEC on slack.com."

Twitter

The outage was discussed on Twitter. Among other tweets:

"If I'm reading this right, Slack's DNS admins may have caused a sitewide outage; they apparently enabled DNSSEC (DS + keys), then disabled (pulling DS + keys), but the DS is cached and DNSSEC-aware resolvers freak out when they can't find the keys." — Thomas H. Ptacek (@tqbf)

"Slack tried to enable DNSSEC, and then tried to revert, taking their zone down. lists.dns-oarc.net/pipermail/dns-... This one is fixable! Use a resolver that doesn't break for DNSSEC! 9.9.9.10 is a good one. It also comes in DoH!" — Filippo Valsorda (@FiloSottile)