191–200 of 721 posts
Just to be clear, this is a DDoS against Dynect's NS hosts, right? I'm confused because of the use of "dyn dns", which to me means dns for hosts that don't have static ip addresses. I'm actually surprised so many big-name sites rely on Dynect, which I hadn't heard of, but more importantly don't seem to use someone else's NS hosts as 2nd or 4th entries.
It may not be the proper action but this kind of soft-fail scenario (use the old DNS until you can contact the DNS servers and get new ones) is much better.
echo "nameserver 208.67.222.222" | sudo tee -a /etc/resolv.confJust to be clear, this is a DDoS against Dynect's NS hosts, right? I'm confused because of the use of "dyn dns", which to me means dns for hosts that don't have static ip addresses. I'm actually surprised so many big-name sites rely on Dynect, which I hadn't heard of, but more importantly don't seem to use someone else's NS hosts as 2nd or 4th entries.
The company is just called "Dyn", DynECT is a product name, but yes.
Seems to be impacting POPs in US East most severly. We use Ripe Atlas to assess the impact of DNS outages, and in the past hour have measured about 50-60% recursive query failure from a few hundred probes in that region: https://cloudharmony.com/status-for-dyn
I can't currently get resolution on www.paypal.com. $ dig @8.8.8.8 www.paypal.com ; > DiG 9.8.1-P1 > @8.8.8.8 www.paypal.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER ;; QUESTION SECTION: ;www.paypal.com. IN A ;; Query time: 29 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Fri Oct 21 12:35:33 2016 ;; MSG SIZE rcvd: 32
Also, I'm unable to resolve Twitter on TWC dns.