4 ms·
So it's a double cancellation of it that bring it back to the original phrase? To show that they didn't take it seriously because it isn't actually true, but th
by AlecSchueler 3y ago
So it's a double cancellation of it that bring it back to the original phrase? To show that they didn't take it seriously because it isn't actually true, but then they found it was true in this case, or at least it felt true if all other cases were ignored? Like it was sorta true but not completely since another problem might have had a non DNS issue at its source?
I feel like I see what they're saying but I'm still confused at what's getting communicated. Just "sometimes DNS can actually be a source of problems?"
- kseifried 3y agoFrom many years ago on the #osspodcast Episode 184 – It’s DNS. It’s always DNS https://opensourcesecurity.io/2020/02/24/episode-184-its-dns-its-always-dns/ https://opensourcesecurity.io/2020/02/24/episode-184-its-dns... If you look at a lot of outages and incidents, DNS is a common problem.
- AlecSchueler 3y agoSo a better headline might have been "It is, indeed, always DNS?"
- froggit 3y agoExcept that would be factually incorrect. The title of the article doesn't convey what i would call useful information, but at least it checks out.