We use Amazon Route 53 as our primary DNS and traffic management service to ensure high availability, scalability, and low latency access to our web and cloud-based applications.
Pros
High availability and maximum uptime & fault tolerance
Global performance optimization using latency based routing
scalability as Amazon Route 53 can auto scale to handle increased DNS queries
Cons
Limited real time statistics and monioring
Complex configuration for advanced routing polices
Limited integration with On-premises infra
Likelihood to Recommend
Amazon Route 53 is well suited for global application load distribution. As in we had customer-facing service hosted in 2 aws regions - Mumbai and Singapore. Using Amazon Route 53 Latency Based Routing we automatically directed users to the region with the lowest latency for users from Asia. Thus LBR improved response by about 28-30%.
VU
Verified User
Engineer in Information Technology (201-500 employees)
Amazon Route 53 has a simple UI with everything you need right in front of you. When you add a new record, the response time is super fast. Support for elastic DNS is also fantastic, as setting anything like that up manually requires knowledge, whereas Route53 provides it ready-made availability.
Pros
Super fast DNS server.
Quick setup.
Large API Library.
Cons
Needed bit easy documentation.
GUI could be better with more themes.
Likelihood to Recommend
Route53 is fully accountable for our product DNS hosting and monitoring. It has boosted uptime and made administration easier. It's also simple to automate and monitor, making it easier to manage operational difficulties and development.
Amazon Route 53 is an excellent tool for DNS routing that is simple to set up. Setting up your domain with DNS servers and DNS routing in minutes takes virtually no time. Route 53 is ideal for all sizes of businesses, all types of industries, and all regions of countries.
Pros
DNS Customization
Easy to Integrate
Low Cost Service provider
Cons
interface is a bit basic
Cheap for first year but costly for renewals
Likelihood to Recommend
We decrease the time spent on operational tasks and utilize it to focus on development tasks, which cannot be archived without the assistance of a service provider such as Amazon Route 53. It's so inexpensive and affordable that anyone can get started with it, yet it's a highly dependable tool.
Our backend services run in AWS, and we need public domain to expose the services. The services are running in different geo locations as we have end users globally. But we would like to provide one single domain to end users. With the routing features from Amazon Route 53, we are able to route the requests to nearest location from the user, which reduces latency and improves user experience.
Pros
Routing policy support
Seamless integration with other AWS services
Support for Infrastructure as Code
Cons
Probably better monitoring of user traffic
Likelihood to Recommend
Amazon Route 53 is well suited if: 1. you always use other AWS services, and need good integration for some DNS service 2. you need support for simple traffic routing, e.g. based on latency or geolocation 3. you need support for complex traffic routing 4. you want to manage DNS via code
Ease of use and management of the amazon route 53 that is our main benefit. Our current solution was not cloud based and it would affect us geographically. But Route 53 being a cloud service has greatly helped us in that space. We use it for managing the external DNS services within our organization.
Pros
It help us increase dependability by rerouting our DNS to an alternate destination if the original application endpoint becomes unavailable.
Amazon Route 53 on Amazon Traffic Flow directs the traffic depending on a variety of factors, including endpoint health, geographic location, and latency which we set up various traffic regulations and choose which ones to use at any given moment.
We can build and change traffic policies via the Route 53 interface, AWS SDKs, or the Route 53 API using the easy visual editor So, the versioning function in Traffic Flow keeps track of changes to traffic policies, allowing us to quickly roll back to a prior version through the interface or API and thus it provides flexibility.
Cons
more customization or interface options
Model registry may be not clear sometimes.
Likelihood to Recommend
- 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.
VU
Verified User
Engineer in Information Technology (5001-10,000 employees)
We have been using Amazon Route 53 in order to redirect our end users to our applications, using their capability of translating human language to our IP addresses. Before using Route 53, we were facing a lot of issues regarding routes and DNS which now is much easier to set up and follow up.
Pros
Easy setup
Running on AWS environment
Cons
Charts
Follow-ups
Likelihood to Recommend
If you want to get rid of route issues and you are hosting your applications on AWS Cloud, Amazon Route 53 is definitely a good choice once it is very easy to set up and you don't need to worry anymore regarding the routes and DNS settings once this tool handles all these things for you.
VU
Verified User
Analyst in Information Technology (10,001+ employees)
We use Amazon Route 53 to provide public DNS services for several domains for our public websites, remote access with health checks, and for other common services. We needed a global and reliable provider that had a lot of functionality and could work well with our public website, which is also hosted on AWS.
Pros
Reliable
Cost effective
Integrates with other AWS services
Cons
Flexibility
Usability
Likelihood to Recommend
Great for customers who have a decent understanding of how DNS works and need a global & reliable service. Also helpful for customers looking for an integrated solution that can pair well with other AWS services, such as EC2 for website hosting. Not as good for customers that want an extremely simple, plug and play solution (don't get me wrong though, Route53 isn't SO difficult).
VU
Verified User
Engineer in Information Technology (201-500 employees)
Highly Available, scriptable DNS zone management. We had issues with DOS on smaller providers (Ultra, Dyn) and Amazon Route 53 was able to handle DDOS against our zones better.
Pros
API access to manage Amazon Route 53
Redundancy and High Availablility
Nice extensions (geographic resolution, aliasing)
Cons
As long as all Amazon Route 53 can be controlled when us-east-1 is down, I'm happy.
Replication lags but don't they all?
Diagnostics on DNS TXT validation fields like "issuewild" is suddnly necessary but was never really documented as a "change" to their requirements.
Likelihood to Recommend
Very redundant, very fast, very easy to use the API, and very cheap.
VU
Verified User
Engineer in Information Technology (201-500 employees)
We use AWS Route 53 as the DNS management solution for ~12 years. We have over 800+ domain entries being managed over there. These include the tools as below:
API Endpoints that process over 100M API calls a day.
Web-Portal for configuration management used by 20K business users.
Web-hooks exposed to the external world for sending DLR notifications for the marketing messages that we send out (>100M messages per day).
Pros
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.
Cons
Importing external Zone files is tricky. Takes a bit of time to figure.
UI is a little slow to load when the number of entries are high (>100)
Can give tag based search feature to make it easier to look for the relevant entries.
Some common features like Logging, Health Checks can be expensive.
Likelihood to Recommend
Services needed high availability - It's always available (nearly). Haven't had too many major outages in the last 12 years. Working with Infrastructure as a Code platforms - Great API support that makes is easier to work with external infra management tools. Auto-Failover, and Advanced Routing - Good support for failovers and routing policies that can be mixed and matched. Different Network topologies - You can create internal VPC's and external look-ups seamlessly using the same set of tools.
I am using amazon rote 53 as a delegated Nameserver from my primary DNS server. This is acting as a backup DNS incase if the primary goes down
Pros
high availability
easy to generate the hit count report
uptime
Cons
it took time initially to setup the synchronization from my primary DNS to route 53
cost is based on the usage/hit count
Likelihood to Recommend
when we had a issue with the primary DNS provider due to DDOS attack, the route 53 served all the DNS request and thus having a minimum impact to our business. There is no specific reason for choosing aws DNS but since we had this for almost 7 - 8 years , we never though of changing it to something else as we never encountered any issue with route 53
