Amazon Route 53 is a Cloud Domain Name System (DNS) offered by Amazon AWS as a reliable way to route visitors to web applications and other site traffic to locations within a company's infrastructure, which can be configured to monitor the health and performance of traffic and endpoints in the network.
$0.40
Per Zone Per Month
Pricing
Amazon Route 53
Editions & Modules
Standard
$0.40
Per Zone Per Month
Queries
$0.60
Per Million Queries
Offerings
Pricing Offerings
Amazon Route 53
Free Trial
No
Free/Freemium Version
No
Premium Consulting/Integration Services
No
Entry-level Setup Fee
No setup fee
Additional Details
—
More Pricing Information
Community Pulse
Amazon Route 53
Considered Both Products
Amazon Route 53
Verified User
Analyst
Chose Amazon Route 53
We didn't test any other product like Amazon Route 53, we were doing all these settings by ourselves.
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, …
Amazon is priced higher than Google's DNS, but since our gear (Cloudfront, ALB, etc) is in AWS, Amazon Route 53 is easier to use sop we don't have to manage two vendors.
Cloudflare is also similar in the features to Route 53. However, since we are completely hosted on the AWS cloud, we can't use Cloudflare for configuring our internal networks, and integrating with the other services. The API based integration of AWS via Terraform is another …
Amazon Route 53 DNS service is much better than GCP and Azure or any other cloud provider DNS service due to the fact that it not only provides basic DNS service but on top of it it offers firewall DNS feature i.e. rules and policies can be defined to allow/reject certain …
Since we are heavy users of AWS, it was only natural for us to go with Route53. It's well integrated with other AWS services, and domain creation and modifications can get automated with the infrastructure itself, with tools like terraform.
Amazon Route 53 is intended for simple websites that host HTML5 or static content. This is probably the default solution if you need something simple and don't want to rent a web server to host a website. It is good to host full functional but simple website or HTML5 game.
When working with AWS, Route 53 is hands down the better solution. If you live in GCP, then Google Cloud DNS is the way to go. GoDaddy is more of a consumer-facing product and is perfectly fine when Services are not being utilized in any Cloud Environment. Eventually, all of …
GoDaddy is fine if you just want to have a domain and set up a few simple records. But if part of your business is transferring domains and constantly updating records for new websites, email changes, and security, then a registrar-based DNS service just won't cut it. Route 53 …
Route 53 is one of those essential services that you'll inevitably come across. It's one of the easiest to understand and configure in AWS, and using it is helpful if you're making use of any other components in the AWS ecosystem because most other components will …
Both Azure DNS and GoDaddy's DNS works great, but when you use AWS services and infrastructure, it is much easier to use AWS DNS service. Using AWS DNS service you can manage and maintain your infrastructure in one place, it saves some time. If you use AWS services, you can …
Infoblox is the one we used on premises and briefly looked at for AWS. Route 53 however is well suited for our needs and was easier to implement. As AWS was already new for use, learning Route 53 anew made no difference in selecting it.
Route 53 is head and shoulders above GoDaddy. GoDaddy's DNS availability was problematic with us earlier on and at that time we made a decision to move our domains to Route 53 under Amazon. Since then we haven't experienced any DNS outages and it has been pretty rock solid. …
Route53 was used because I initially thought we were going to have our infrastructure on AWS. Once our team transitioned to Google Cloud, I was left scrambling to migrate our DNS solution to point to those servers instead. Because there is a mandatory 45-day transfer wait …
I have experience running several on-site DNS services such as PowerDNS, djbdns, bind, and others. Route 53 removes the need to manage the server and DNS software, allowing you to focus on the DNS content itself.
- 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.
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.
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.
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
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!
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.