Follow

DynDNS DDoS Attack - October 21st, 2016

UPDATE - 10/21/2016 7:15PM EST

As of 22:17 UTC, DynDNS has stated the DDoS attack affecting their infrastructure has been resolved. Distil Networks is currently verifying the resolution for all our customers using the Dyn network. We are working closely with Dyn to insure we receive a full RCA for today’s events. The entire Distil Networks team is committed to providing high quality service and we regret the impact from today’s incident. We expect service to be restored and operating normally for everyone within the next fifteen minutes.

-------------------------------------------------------------------

UPDATE - 10/21/2016 6:35PM EST

As of 6:35pm EST, Dyn states the issue is resolved, we are currently verifying.

-------------------------------------------------------------------

UPDATE - 10/21/2016 5:45PM EST

We have begun the migration of Domains affected by the DynDNS DDoS event to a new provider. We expect these migrations to be occurring fairly quickly but do not have an exact ETA on completion. Our team will continue to monitor the network and also continue to make improvements to stability and performance. We will provide another update after the migrations are completed.

-------------------------------------------------------------------

UPDATE - 10/21/2016 3:15PM EST

We are continuing our efforts to mitigate the impact of the Dyn DNS outage caused by the ongoing DDoS against their network. We are now in the final stages of testing a secondary DNS provider and will begin migrating Distil protect domains to the secondary network within the next hour.  We believe this will allow for the continuation of services and web traffic to your sites.

-------------------------------------------------------------------

UPDATE - 10/21/2016 1:15PM EST

As you may or may not be aware, our DNS provider DynDNS, is currently under a severe DDoS attack. Dyn has posted information about the issue here.

At this time Distil Networks is also being adversely affected by this attack. We are currently in contact with DynDNS to ensure resolution as quickly as possible.
If you are public cloud customer, in order to mitigate impact to your own domains, we recommend adjusting your domain’s DNS settings to go from pointing to a Distil CNAME pointing to ‘YourDomain.com.distil.us’ to an A record with an IP address from Distil’s global Anycast IP network as listed below. You can also choose to bypass Distil by pointing your Domain directly to your origin server. We are also working as quickly as possible to add a secondary provider to global DNS network so that DNS resolution can resume if you can’t make the recommended Domain changes on your own for whatever reasons.

Distil Anycast IP Address Instructions:

  1. Change your A record for YourDomain.com to point to 192.225.209.8 
  2. Change your A record for www.YourDomain.com to point to 192.225.209.8

Distil Bypass Instructions:

  1. Change your A record for YourDomain.com to point to your web server IP Address.
  2. Change your A record for www.YourDomain.com to point to your web server IP Address.

Please let us know if you have any questions at all.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments