Dyn.com DDoS Attack
Dyn.com, a popular dynmic DNS provider and provider of commercial managed DNS services is currently experiencing a massice DDoS attack. As a result, many sites that are using Dyn.com's services are experiencing issues.
Affected are not just home/hobby sites that traditionally use dynamic DNS services, but also large "name brand" sites that use Dyn.com's managed DNS service. For example Twitter, Spotify, Etsry, Github and others (domains hosted by Dyn.com often use *.dynect.net name servers)
You can find status updates from Dyn.com here: https://www.dynstatus.com
Keywords:
9 comment(s)
My next class:
Network Monitoring and Threat Detection In-Depth | Singapore | Nov 18th - Nov 23rd 2024 |
×
Diary Archives
Comments
Anonymous
Oct 21st 2016
8 years ago
Anonymous
Oct 21st 2016
8 years ago
Anonymous
Oct 21st 2016
8 years ago
Anonymous
Oct 21st 2016
8 years ago
If a site is well protected, the attacker can still bring it offline by attacking the name servers.
Most company sites have anti-DDoS protection, but how well do they secure their DNS services?
Will we see more attacks via a company's DNS servers?
Something to think about...
Anonymous
Oct 22nd 2016
8 years ago
Some of the affected sites "rely" on DYN, and some "use" DYN ...
CNBC.com nameserver = ns1.p24.dynect.net
CNBC.com nameserver = ns2.p24.dynect.net
CNBC.com nameserver = ns3.p24.dynect.net
CNBC.com nameserver = ns4.p24.dynect.net
Amazon.com nameserver = ns1.p31.dynect.net
Amazon.com nameserver = ns2.p31.dynect.net
Amazon.com nameserver = ns3.p31.dynect.net
Amazon.com nameserver = ns4.p31.dynect.net
Amazon.com nameserver = pdns1.ultradns.net
Amazon.com nameserver = pdns6.ultradns.co.uk
Twitter.com nameserver = ns1.p34.dynect.net
Twitter.com nameserver = ns2.p34.dynect.net
Twitter.com nameserver = ns3.p34.dynect.net
Twitter.com nameserver = ns4.p34.dynect.net
Spotify.com nameserver = ns2.Spotify.com
Spotify.com nameserver = ns3.Spotify.com
Spotify.com nameserver = ns4.Spotify.com
Spotify.com nameserver = ns5.Spotify.com
PayPal.com nameserver = ns1.p57.dynect.net
PayPal.com nameserver = ns2.p57.dynect.net
PayPal.com nameserver = pdns100.ultradns.net
PayPal.com nameserver = pdns100.ultradns.com
PayPal.com nameserver = ppns1.phx.PayPal.com
PayPal.com nameserver = ppns2.phx.PayPal.com
Netflix.com nameserver = ns-81.awsdns-10.com
Netflix.com nameserver = ns-659.awsdns-18.net
Netflix.com nameserver = ns-1372.awsdns-43.org
Netflix.com nameserver = ns-1984.awsdns-56.co.uk
Hmm. SPOTIFY (currently) has no reliance on DYN. Did they migrate away?
Anonymous
Oct 22nd 2016
8 years ago
Anonymous
Oct 22nd 2016
8 years ago
Anonymous
Oct 24th 2016
8 years ago
Anonymous
Oct 24th 2016
8 years ago