👀
(twitter.com)
You're viewing a single comment thread. View all comments, or full comment thread.
Comments (49)
sorted by:
DNS is kind of like how GPS gives you friendly directions. It gives you human readable directions to your destination. Can you imagine if you had to enter GPS coordinates when you just want to find 1234 Great Rd.
However with DNS there is no one mega server under a volcano that controls the internet, rather its a network of systems that all collaborate with eachother. "hey I know where those coordinates go to, heres how I know and also tell every one you know that we know"
Some one or some thing decided to just forget how to get to a certain destination and somehow that forgetfulness got passed on and no one caught it. Or the forgetfulness hit all the systems at the same time before they could update eachother with the real directions.
I guess that's the great discussion. Regardless of what officially happened, things like this have happened before and will continue to happen.
One server going down, blown up, pulled into a blackhole, or whatever would not bring the entirey of DNS down. There is no one ring to rule them all in DNS so a change in one would not affect the rest. But there is a main group (I forgot how many) of authoritative DNS servers that all the other DNS servers look to. And they are spread out geographically all over the world. So that's why when you see things happen like this sometimes a site it down in Europe but everything is fine in the USA.
So something happened to those main DNS servers. I don't know where disclose.tv got their information from regarding the entry being removed.
Malicious? Hell of a feat to pull off on a global scale.
Intentional? Good conspiracy route. Maybe theres something to be disrupted on purpose. Maybe an agenda is being played out. WEF said a global cyber attack was going to be the next big thing.
Accidental is most logical, but it would need to be combined with stupid. So maybe a config was changed or an update performed on a main authoritative DNS server. And in that process something got corrupted or stepped on or changed, then no one noticed it and allowed the error to replicated.
It's not out of reason if there was a big update or patch in a piece of software or a firmware update on a piece of hardware then it would need to be performed on all of the affected software and/or hardware. So if a bunch of DNS servers all got patched at or around the same time and some "entries" got bumped then a bunch of DNSs at the same time are starting to replicate bad information. Again, stupidity here to patch all mission critical things at the same time and not simulate it before deploying the patch to a live environment. Unfortunately IT is one of the first things to be cut at businesses in the name of cost savings.
Very well written analysis fren