3 ms·
From what I can tell, the problem was not caused by DNSSEC directly. It was caused by: 1. A bug in Route 53 which caused wildcard record not to work with DNSS
by teddyh 5y ago
From what I can tell, the problem was not caused by DNSSEC directly. It was caused by:
1. A bug in Route 53 which caused wildcard record not to work with DNSSEC signing. Anyone not using Route 53 would not have had any problems with DNSSEC.
2. Slack decided to revert the DNSSEC rollout, but botched the process badly, effectively locking themselves in the trunk and throwing away the key. If they hadn’t tried to revert the DNSSEC rollout, or if they had been a bit more deliberate and careful while doing it, this would not have happened.
- native_samples 5y agoThe issue wasn't really lacking deliberateness or care but rather that they had adopted a culture of over automation. Why are they using Terraform to make changes that are rare and critical instead of the GUI? The whole point of a GUI is to make computers easier and safer to use, but if you insist on accepting everything then you lose that.