About 5 years in production with Dyn DNS.
Haim Ari | TrustRadius Reviewer
December 10, 2018

About 5 years in production with Dyn DNS.

Score 9 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Oracle Dyn Managed DNS

We use Dyn to distribute traffic across multiple data-centers and to failover automatically between them.
  • Traffic director works well when shifting traffic to different Data-centers according to end user source IP.
  • Active failover provides an easy way to failover between dc when specific health check fails.
  • DNS records updates are published fast.
  • API - working with DSF ID is not fun.
  • Python SDK is not complete, and updating an existing record should be done with less code.
  • When we started using AutoScale Groups in AWS, we utilized Dyn API so that each new launched instances created it's own ID and remove it when it terminates.
  • ActiveFailover allows us to quickly migrate all users to DR site in case it's down very fast. Speed is important and in this case Dyn does the job pretty well.
Before dyn we used Bind dns which does not have "smart" services or an API.
Currently we use Dyn + NS1 in production
The support usually will solve issues, but opening a case can't be done via chat which is a downside.
The UI is well... old. the API and SDK could be better when comparing this to NS1 for example.
After a few years of usage I would say that the best "feature" of Dyn is: availability.
For quick setup of multiple data centers as your service "origins". It is easy to direct users to the closest location of your servers using traffic director and always keep the service up using using active failover.