Amazon Route 53 vs. Oracle Dyn Managed DNS

- Routing users to the closest or best-performing resources: Route 53 allows you to use geolocation and latency-based routing to route users to the resources that will give them the best performance. - Load balancing: Route 53 can be used to distribute incoming traffic across multiple resources, such as Amazon Elastic Compute Cloud (EC2) instances or Amazon Elastic Container Service (ECS) tasks, to improve the availability and scalability of your application. - Managing domain names: Route 53 can be used to register domain names and manage DNS records, making it a one-stop solution for managing your domain name and routing traffic to your resources. Scenarios where Route 53 is less appropriate include:Applications with very high query rates: Route 53 is designed to handle millions of queries per second, but if your application generates an extremely high query rate, you may need to use a specialized DNS service.Applications that require very low latency: Route 53 is designed to provide low-latency DNS service, but if your application requires ultra-low latency, you may need to use a specialized DNS service or a self-hosted DNS solution.Applications that require advanced security features: Route 53 provides basic security features such as DNSSEC, but if your application requires advanced security features such as DDoS protection, you may need to use a specialized DNS service.

Incentivized

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.

Incentivized

• Uptime - Route53 is highly performant and available. We have had only 3-4 instances in the last 12 years when we had any downtime or outages due to Route53.
• Extensive API layer on Route53 that allows integration with external tools and SDK's (Boto, Terraform, etc)
• Closely integrated with the other AWS services. Makes it easy to operate the infra.

Incentivized

• The portal management is very easy to use in comparison to other companies for DNS management.
• The have expert mode that allows for multiple edits on records and allows you to make notes for each edit on a zone.
• The have TTLs that are as low as 30 seconds.

Incentivized

• During initial setup when you are using Route 53 or DNS systems for very first time, there are little number of documentation from AWS which is kinda of little tough. But, once you get hold of it, its a cake walk for everyone.
• Health checks are kinda of little costly when Compared to other big players, but that doesn't affect much when you compare its uses.
• The logging is well structured though its costly

Incentivized

• Simpler billing interface
• 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.

Incentivized

It does exactly what we need, its fast, secure and reliable.

Incentivized

You need to know what DNS is; this is a tool built for developers who already know the technology and are just looking for a DNS management tool. The tool is very usable given that. If you're not familiar with DNS, Route53 isn't really for you and you won't find it to be very usable-- you'll need to go read the documentation, and that will start with learning what DNS is

Incentivized

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.

Incentivized

Until today, I have never needed support to Route53 because the documentation is great. But, I have needed it for other services. And they're near perfect always. Except that they don't have Portuguese support yet and they're sometimes slow to answer (48 hours in non-critical ones, in two tickets). But usually, they're amazing!

Incentivized

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

Incentivized

We purchased our domain names through Networksolutions.com and do rely on their DNS services for basic functionality (SPF hard reject records, etc.), since it was included at no cost; however, for our main domains, we utilize Route 53 because of AWS's high availability, reasonable cost, and capabilities to integrate with EC2 and other security certificate services to make hosting on AWS simple. We also front-end some of our sites with Cloudflare and while it's not as streamlined as using AWS natively, it does a good job.

Incentivized

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.

Incentivized

• All of our brand domain names (about 80 brands) are managed in there
• Many non marketing or brand domains are also in there
• There isn't any defined ROI because it's such a trivial and necessary service with impacts all business operations

Incentivized

• 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.

Incentivized