Why Friday's Massive DDoS Attack Should Be Terrifying

Ok, dumb question:<p>Why can&#x27;t a list of addresses of all the devices in the world of the type used in the attack be created, and all packets from any address on the list be trashed? At least, for the duration of the attack.<p>If such lists were made ahead of time, they could be turned on rapidly.<p>Is anything like this done?

Reddit, Netflix, Github and Airbnb all appear to have switched from Dyn to AWS DNS for their primary .com domains by now.

&#x2F;etc&#x2F;hosts saved the day for me.

I&#x27;m not aware of all the technical intricacies here, but could this kind of attack be preventable by having local DNS caches in the OS itself, kinda like a dynamic hosts file?

It should be terrifying because the government&#x27;s complete lack of ability to regulate anything has allowed the so-called &quot;internet of things,&quot; more accurately called the &quot;internet of corporate things that the user is locked out of,&quot; to develop into a national security threat.

Do we know who is behind this?

90 miles from Chicago. Didn&#x27;t notice a thing.<p>Note: I&#x27;m not dismissing the validity of the concern. I&#x27;m only reporting that I didn&#x27;t even know about it as the attack was happening. I&#x27;m sure others were much more severely affected.

Friday&#x27;s massive ddos attack barely registered on my day-to-day, the only annoyance was that Github was slightly slower than usual. It has been amusing though to see all the hundreds of news articles trying desperately to sensationalize the event.. and it simply didn&#x27;t even matter.