Author

Topic: Big DDoS Attack on DNS,Major sites including GitHub,Twitter Suffering Outage (Read 467 times)

sr. member
Activity: 430
Merit: 250
The question is: who carried out this attack and what are the techniques used in it?
Vod
legendary
Activity: 3668
Merit: 3010
Licking my boob since 1970
Imagine a scenario where a DNS provider that is used by Reddit, Twitter or Facebook is under DDoS attack, there is no way a user can visit any of these sites

That's not exactly how DNS works.  Instead of "a user" you should have written "a new user".  Users that have visited the site before would have the IP address cached for a period of time, and would not need to talk to a DNS server.
sr. member
Activity: 374
Merit: 250
I just tried to go to CNN.com with their IP address, but instead get an error. Though going straight to cnn.com works. Interesting.
sr. member
Activity: 430
Merit: 250

MAJOR WEBSITES HAVE GONE DOWN WORLDWIDE — THE REASON IS STILL UNCLEAR BUT A MAJOR DNS PROVIDER IS SUFFERING A MASSIVE DDOS ATTACK AND EXPERTS ARE CONNECTING THE DOTS.

Imagine a scenario where a DNS provider that is used by Reddit, Twitter or Facebook is under DDoS attack, there is no way a user can visit any of these sites and it looks like that’s what’s going on right now. There are several websites that were down this morning including Twitter, Reddit, Spotify, Esty, Box, Wix Customer Sites Squarespace Customer Sites, Shopify, SoundCloud, Github, Airbnb, Reddit, Freshbooks and Heroku. However, some sites are already coming back online.

In a statement, Dyn acknowledged that their servers are under DDoS attack.

Starting at 11:10 UTC on October 21th-Friday 2016 we began monitoring and mitigating a DDoS attack against our Dyn Managed DNS infrastructure. Some customers may experience increased DNS query latency and delayed zone propagation during this time. Updates will be posted as information becomes available. This attack is mainly impacting US East and is impacting Managed DNS customer in this region. Our Engineers are continuing to work on mitigating this issue.
Jump to: