For everyone currently rushing to move their DNS records away from Dyn to alternative providers; don't panic.
Moving your DNS isn't hard, but is basically a hit-or-miss: it either works or it doesn't. I'm working on a tool to help monitor DNS changes that can help in migration scenario's by letting you know if any unwanted DNS records have changed.
I'm looking for any feedback you may have, you can sign up for the beta here: https://dnsspy.io/
(Ps; it seems shameless to plug a new service in a thread where a company just got bought, but I truly believe it can help ease the migration pain some may be feeling. Feel free to downvote if it makes no sense here or if it's just too blunt. Apologies, in that case.)
DYN did a lot more than just Authoritative DNS. They did monitoring that then would facilitate a failover to different hosting environments, creating a quick active active or active passive failover depending on your configuration. They offered this with a complete web GUI that had permission controls that were granular so newer techs or less technical employees could login and manage just a single record or series of records.
Not to mention their solutions are very fast.
I'm not aware of any other dns host that does all of this.
This only applies if you used Dyn as a DNS provider with DDoS protection, not if you've used any of their failover capacity.
Having said that, I also don't think people should rush to get away from Dyn. Take your time, evaluate the buy and see where the service goes in a few months. If nothing changes for you, why even bother changing?
Route53, Azure, and NSOne have it already. CloudFlare is about to have it too. Google Cloud solves this with global load balancers if you're running in their cloud.
There are several other DNS providers that have varying levels of this functionality. There is nothing unique about Dyn except their pricing.
Most users just don't care about DNS, so they use their domain-registrars' offerings (which are frequently terrible). The people who do care seem to pick their provider based on either price, or on features such as non-standard record types (the various different hacks to allow top-level CNAMES, or the ability to return different results on a GeoIP basis.)
Once you start relying on these special things moving becomes hard - because different providers either don't offer them or don't offer them the same way.
I picked up a few new users at the last Dyn DDoS attack; I'm actually surprised many (Dyn) customers moved away entirely. To get redundancy users should add their DNS records to, say, Route53 AND Dyn, not just jump-ship to a new provider.
Those who've joined the beta waiting list (by entering their e-mail address on the homepage) should get in within days. But I also don't want to rush things and break functionality, so I'm still being careful here.
Moving your DNS isn't hard, but is basically a hit-or-miss: it either works or it doesn't. I'm working on a tool to help monitor DNS changes that can help in migration scenario's by letting you know if any unwanted DNS records have changed.
I'm looking for any feedback you may have, you can sign up for the beta here: https://dnsspy.io/
(Ps; it seems shameless to plug a new service in a thread where a company just got bought, but I truly believe it can help ease the migration pain some may be feeling. Feel free to downvote if it makes no sense here or if it's just too blunt. Apologies, in that case.)