Oracle Dyn DNS (domain name system) is an infrastructure-as-a-service that is touted by Oracle Dyne as one of the highest performance global networks existent. It is available as a managed DNS with secondary DNS available for more reliable business continuity on higher service tiers.
As our organization had an ample amount of DNS to manage, it was quite inconvenient when it comes to Amazon Route 53 or any other alternatives as the change propagation time was pretty much high as compared to Oracle Dyn Managed DNS. And when it comes to the huge customer base …
Oracle Dyn Managed DNS is much simpler to use and has no ads. Using other companies, you sometimes have pop-up ads and have difficulty getting to the zone and managing the DNS records. Since Dyn Managed DNS is only DNS, you're in, out, done. No time is wasted trying to …
Name.com also has DNS management but I think Dyn does a much better job. The layout of the website is more intuitive and actually loads and performs much better. Overall if you have a domain name on name.com that you use, I would transfer it to Dyn as its easier to use.
We have been using Dyn since before it was acquired by Oracle and has never failed us. I have used other DNS providers in the past, mostly from the domain registrars, but those have lacked features and availability of certain types of DNS records. In addition, the management …
We selected it for stability. It has a way better UI than UltraDNS. Oracle Dyn has a clear user interface without bloatware, and the actions don't surprise you.
Route 53 - Their main benefit is the integration with the rest of the Amazon Web Services suite, something other …
We actually use both providers, but Dyn is our primary.
In terms of feature set, both companies have very similar offerings. We've found Verisign's UI and documentation to be overall more usable, but Dyn's GeoDNS management is far simpler. Both companies offer an API, and while …
We have not evaluated any alternatives recently. Previously we managed DNS at a registrar, and their lack of options made us realize we needed to find something better.
Oracle managed DNS becomes very heavy when there is an ample amount of DNS being managed. However, the DNS creation and updating takes very less time to propagate and is very easy to use. So, for an organization, where there is a modest amount of DNS to manage, it works very well and gives a splendid experience. So, considering the complexity of managing the DNS for an IT company Oracle Dyn managed DNS is the best option to opt.
More responsive sales team to provide relevant QBRs to ensure proper and best practice use of the product/platform
Integration of the Dyn ECT Managed DNS with Dyn Domain Registration would be a nice feature as currently I have to manage two consoles and billing accounts.
This is the only real gripe we have with Dyn; their web-UI can be remarkably painful to use. In the "simple" editor, DNS records are arranged in a kind of "node" view, where each record is a node and any records of the same name or longer (i.e. all records called "record.example.com" or "other.record.example.com") fall under it. This creates an odd sort of hierarchical view that's not really representative of the zone file. The "expert" editor doesn't have an actual delete button, just a checkbox. If you want to update conflicting record types (for example, replacing an A record with a CNAME) you have to check the box for the record being deleted, save changes, create the new record, save changes, and finally publish changes. Dyn uses a publish model for changes, where all changes you make are staged and can be reverted or published all at once. This is fine, except that the publish/revert dialog is in a different page. This is nice when you have many changes, but very annoying when you're changing just one or two records across multiple zones. These are relatively minor issues in an otherwise good platform; annoyances more than deal breakers.
The support team at Dyn has always been very helpful and have tried to answer our questions to the best of their knowledge. We have never had any issues from support tickets and they are often resolved in a few hours
We use both Oracle Dyn Managed DNS and Amazon Route 53. We like having our main DNS provider outside our cloud provider in case there's an issue with Amazon and we need to point things somewhere else temporarily. But for all the smaller stuff and internal stuff, we use Route 53 successfully.
For the law firm its being used for, it keeps their remote users working. For law firms, time is money, usually every 15 minutes lost can be a big deal to them.
Sometimes it has switched when its not supposed to, and causes downtime. No real way to inform users when the switch is happening, it would be great to have an email alert we can not only send to ourselves but a notification to primary and technical partners in the firm so they don't have to yell at us like something is broken, instead they are aware it had to change.