Kitz Forum
Announcements => News Articles => Topic started by: kitz on October 21, 2016, 07:12:15 PM
-
Ive been attempting to get to paypal to pay a bill, but their website wouldnt load as server not found for the past few hours.
Then I noticed various other large US based sites were also unobtainable. ie twitter
downforeveryoneorjustme (http://downforeveryoneorjustme.com/paypal.com) was exceedingly slow to load for some reason. But when it eventually did load it said "paypal.com' is up.
Yet isitdownrightnow (http://www.isitdownrightnow.com/paypal.com.html) says 'paypal is down for everyone'.
Tracerts showed what looks like could be a dns issue.
C:\WINDOWS\system32>tracert www.paypal.com
Unable to resolve target system name www.paypal.com.
C:\WINDOWS\system32>tracert twitter.com
Unable to resolve target system name twitter.com.
Changed my dns settings from google to OpenDNS [208.67.220.220/2-8.67.222.222] and the internet sprang back to life.
-
I've seen something that suggests there is a big DDOS going on.
-
Just found this: http://www.bbc.co.uk/news/technology-37728015 (http://www.bbc.co.uk/news/technology-37728015)
PayPal is specifically mentioned.
-
Thanks. Wonder if they are also attacking googles DNS servers.
Its strange that I couldnt reach many sites when using google's DNS servers, but now Im using OpenDNS everything seems ok.
-
Yeah, a managed DNS provider called Dyn have been experiencing a DDoS attack, which is grinding many websites to a halt. Twitter, Github, PayPal, Ebay, and many others.
http://www.theregister.co.uk/2016/10/21/dns_dyn_ddos/ (http://www.theregister.co.uk/2016/10/21/dns_dyn_ddos/)
https://www.dynstatus.com/ (https://www.dynstatus.com/)
OpenDNS might simply have not cleared their cache yet, or may be sourcing it from a different DNS zone.
There is mention of an escalated attack, but not sure what they meant by this. Could be that they are targeting multiple DNS providers, although Google would be very difficult a target to take down with just a DDoS.
-
I noticed the story in the newspaper this morning and it wasn't effecting UK people. But now it is. PSN is down too. Paypal is listed as well.
I'm getting DNS error and I moved away from Google DNS a few days ago. So its not only Google's DNS.
Hopefully things settle soon.
-
http://gizmodo.com/this-is-probably-why-half-the-internet-shut-down-today-1788062835 (http://gizmodo.com/this-is-probably-why-half-the-internet-shut-down-today-1788062835)
Twitter, Spotify and Reddit, and a huge swath of other websites were down or screwed up this morning. This was happening as hackers unleashed a large distributed denial of service (DDoS) attack on the servers of Dyn, a major DNS host. It’s probably safe to assume that the two situations are related.
Update 12:28 PM EST: Dyn says it is investigating yet another attack, causing the same massive outages experienced this morning. Based on emails from Gizmodo readers, this new wave of attacks seems to be affecting the West Coast of the United States and Europe. It’s so far unclear how the two attacks are related, but the outages are very similar.
-
Just seen this (https://news.ycombinator.com/item?id=12762110)which may in part explain why OpenDNS is working?
Out of curiosity, why do caching DNS resolvers, such as the DNS resolver I run on my home network, not provide an option to retain last-known-good resolutions beyond the authority-provided time to live? In such a configuration, after the TTL expiration, the resolver would attempt to refresh from the authority/upstream provider, but if that attempt fails, the response would be a more graceful failure of returning a last-known-good resolution (perhaps with a flag).
>> OpenDNS does this: It's called SmartCache.
>>> Anyone know if Google Public DNS does?
>>>> It doesn't (first result is openDNS, second is google):
-
Yep OpenDNS do some local caching their end, I realised what was going on when I saw the news article on BBC and added secondary DNS as OpenDNS and thats resolving the addresses - Google's DNS is still failing.
-
Yeah that would explain issues this evening so I added OpenDNS has my secondary server so at least one provider should remain online.
-
This is an analysis from Brian Krebs, whose site along with OVH were subject to the largest DDoS attacks ever seen (620Gbps and 1.2Tbps respectively).
https://krebsonsecurity.com/2016/10/ddos-on-dyn-impacts-twitter-spotify-reddit/ (https://krebsonsecurity.com/2016/10/ddos-on-dyn-impacts-twitter-spotify-reddit/)
-
Article in elreg - link (http://www.theregister.co.uk/2016/10/21/dns_devastation_as_dyn_dies_under_denialofservice_attack/)
After two hours into the initial tidal wave of junk traffic, Dyn announced it had mitigated the assault and service was returning to normal. But the relief was short lived: just about an hour later, the attack resumed
/snip/
OpenDNS is about the only major public DNS provider weathering the storm – if you're having problems connecting to websites, you should use OpenDNS's resolvers at 208.67.222.222 and 208.67.220.220. OpenDNS uses smart caching during outages to keep looking up hostnames even if the websites' backend DNS is flooded off the 'net.
I hadn't seen other articles, I'd tried to pay for something quickly by paypal, but then had to go out, so didnt really have time to look. When I got back it was then I realised it was also affecting some other websites too, and from a tracert it looked like it could be DNS. I just happened to pick OpenDNS because it was the other public DNS that I knew off the top of my head.
Good way to take out the internet - knock out all the major DNS servers :(
In the meantime speculation begins as to who the culprit is and their motive.
-
These companies have made themselves extra vulnerable by the fact they all have very low TTL A records, so dns lookups wont be cached for long.
-
These companies have made themselves extra vulnerable by the fact they all have very low TTL A records, so dns lookups wont be cached for long.
While this could be seen as a vulnerability, it is also an advantage, because as GitHub have done, it aids in the transition to a new provider in lieu of their current provider being attacked.
In terms of this attack, the fallout initially will last a few days I feel, but we will probably see in the long term a lot of companies moving to in house DNS, or moving to providers that actually use DDoS protection in front of their servers that are capable of defeating such large attacks.
-
Are you aware that Dyn DNS are currently suffering a Ddos attack?
https://www.wired.com/2016/10/internet-outage-ddos-dns-dyn/
-
Dyn is a company that provides DNS services. Dyn DNS is short for Dynamic DNS, and is a seperate thing. This thread is talking about the impact of the attack on Dyn the company.
On that note, El Reg released this info from a Dyn spokesperson, confirming suspicions of involvement of the Mirai botnet.
(https://i.gyazo.com/d0bebe354006f5bffa17874d1b79d509.png)
EDIT
An article from El Reg with the full details has been posted.
http://www.theregister.co.uk/2016/10/21/dyn_dns_ddos_explained/?mt=1477082947065 (http://www.theregister.co.uk/2016/10/21/dyn_dns_ddos_explained/?mt=1477082947065)
-
A lot of DDOS problems reported yesterday I think. People were manually changing to Google DNS server 8.8.8.8 to try and avoid the issue apparently.
o7
C
-
OpenDNS is good. Fast and has some nice features. Watch out for the nasty feature of returning false positive responses to queries for an non-existent domain name. That's what they used to do anyway, don't know if they still do. You can turn this non-standards-compliant behaviour off if you create an account and opt out for your IP address range. (It's a long time since I tested the service though.)