Technical Lead - Cloud at a comms service provider with 1,001-5,000 employees
Real User
Top 10
Aug 13, 2025
I am not using AI-driven applications with Amazon Route 53; whatever I do is totally manual work because I haven't introduced AI in Amazon Route 53. The company is not looking into it right now because we need to maintain records, and I don't need AI just to manage my Amazon Route 53. It's obvious AI is good from the application point of view, but from the infrastructure, setting up an AWS cloud infrastructure or GCP infrastructure, meaning Google Cloud infrastructure, I am not fully dependent on AI. My experience is enough to build an IT infrastructure and optimize costs, and that's why I haven't introduced AI. I rate Amazon Route 53 a nine out of ten.
Architect at a financial services firm with 5,001-10,000 employees
Real User
Top 20
May 7, 2025
Amazon Route 53 should ensure a baseline understanding across the board. Improving organizational understanding would enhance customer support. I would rate them around a seven to 7.5 overall.
Lead Software Engineer at a tech services company with 1,001-5,000 employees
Real User
Top 5
Apr 8, 2025
I would recommend Amazon Route 53 for use. Use it for better DNS management, and if you want to route to internal services capable of identifying IP addresses, definitely go for it. I rate the overall solution nine out of ten.
Amazon Route 53 is excellent for those dealing with traffic management and routing services. It's good to use it for your application if you know your traffic flow and latency needs. I rate it an eight out of ten since technical knowledge is needed.
AWS Senior Consultant at a tech services company with 51-200 employees
Consultant
Top 10
Oct 16, 2024
There is no real choice if you want public services to be accessible. However, I recommend using Route 53 for internal private naming spaces as well, as it centralizes management and is easy to manage. I'd rate the solution ten out of ten.
The tool's health check functionality improved our company's service reliability since it is a good feature. Its use still depends on a case-by-case configuration. The tool has certainly fulfilled the basic purpose of monitoring. There is no need to somehow maintain or support the solution. I am not sure how Amazon Route 53 can handle traffic spikes and what difference it has made to our company's service availability. The tool is not difficult to use, and it does what it is meant to do. I rate the tool an eight out of ten.
I would recommend Amazon Route 53 to other users because it can concentrate every configuration on the same platform. Overall, I rate the solution ten out of ten.
We expose DNS to the public, and based on that, we use Amazon Route 53 in our load balancer. Amazon Route 53 provides good traffic management. If we change the IP of any VMs or server to a specific DNS, it gets automatically updated within a time frame and gives a very good exposure to the public. The solution's A record and CNAME record are the most beneficial features for domain registration and management. The solution's health check feature is good because it keeps checking the health of the service. The solution integrates well with other AWS services, load balancers, VMs, or EC2 instances. I would recommend Amazon Route 53 to other users because it is a good tool for traffic flow and DNS mapping. Overall, I rate the solution ten out of ten.
The product can be used for DNS management if a user connects the DNS name with Amazon Route 53. The tool can be used for DNS-related purposes. The product helps our company set up and register domain names. The tool also helps our company to add a domain name address to a website on the browser. The product helps with the traffic flow feature as it allows you to assign CIDR blocks and IP addresses. The tool also helps in the area of DNS queries. The product integrates with other services from AWS, like Amazon S3 bucket and load balancers. The product can also be used with AWS EC2 Instances, AWS Global Accelerator, Amazon SNS, and AWS Lambda. I recommend the product to those who plan to use it. In our company, we use the services of the product without any cloud products. I rate the overall tool an eight out of ten.
Software Engineer DevOps at a financial services firm with 51-200 employees
Real User
Top 10
Mar 5, 2024
For traffic management, the product offers functions similar to other domain name server providers. As an AWS user, having Route 53 as an in-house tool simplifies the entire process, eliminating the need to navigate different platforms for defining the records or other entries. The integration within the AWS ecosystem streamlines the management of DNS services. The most beneficial feature of Route 53 for domain registration, from the engineers' perspective, lies in its seamless integration within the AWS Cloud ecosystem. It becomes easier to manage multiple AWS services in a single platform. The feature for health check efficiently impacts the uptime and reliability of AWS servers including EC2 and EKS. It enables easier traffic routing as compared to GoDaddy. The readiness checks feature ensures that our applications are well-prepared to handle incoming traffic including DNS firewall setup. Also, we can conduct geo-based and latency-based routing. For IT-based routing, they offer a DNS failover feature. I recommend the product to others and rate it a nine out of ten.
I use the latest version of Amazon Route 53. Amazon Route 53 is a cloud-based solution. I would recommend Amazon Route 53 to other users. Overall, I rate Amazon Route 53 a nine out of ten.
Amazon Route 53 is user-friendly for anyone who knows to work with DNS records. Otherwise, they will have to learn about the different kinds of DNS records. Two people in our company do the solution's configuration. I would ask users to use Amazon Route 53 because I haven't faced any problems with it. Overall, I rate Amazon Route 53 a ten out of ten.
I would rate the solution an eight out of ten. The product is better than Cloud DNS. You should use Terraform while using Cloudflare so that you do not need to create manually anything. People usually think that they will use Cloudflare less but end up using it more. The best way to go is to follow a pipeline automated process for testing and production.
I would rate this solution as seven out of ten. Amazon Route 53 is for high availability and scalability. It works well in AWS and handles almost all of the queries. My advice is to use Amazon Route 53, but you need to make sure that it's configured properly because your data and organization could be compromised.
Amazon Route 53 is a highly available and scalable cloud Domain Name System (DNS) web service. It is designed to give developers and businesses an extremely reliable and cost effective way to route end users to Internet applications by translating names like www.example.com into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other. Amazon Route 53 is fully compliant with IPv6 as well.
I am not using AI-driven applications with Amazon Route 53; whatever I do is totally manual work because I haven't introduced AI in Amazon Route 53. The company is not looking into it right now because we need to maintain records, and I don't need AI just to manage my Amazon Route 53. It's obvious AI is good from the application point of view, but from the infrastructure, setting up an AWS cloud infrastructure or GCP infrastructure, meaning Google Cloud infrastructure, I am not fully dependent on AI. My experience is enough to build an IT infrastructure and optimize costs, and that's why I haven't introduced AI. I rate Amazon Route 53 a nine out of ten.
Amazon Route 53 should ensure a baseline understanding across the board. Improving organizational understanding would enhance customer support. I would rate them around a seven to 7.5 overall.
I would recommend Amazon Route 53 for use. Use it for better DNS management, and if you want to route to internal services capable of identifying IP addresses, definitely go for it. I rate the overall solution nine out of ten.
Amazon Route 53 is excellent for those dealing with traffic management and routing services. It's good to use it for your application if you know your traffic flow and latency needs. I rate it an eight out of ten since technical knowledge is needed.
Once the service is configured, it's important to monitor it to ensure traffic is managed effectively. I'd rate the solution eight out of ten.
There is no real choice if you want public services to be accessible. However, I recommend using Route 53 for internal private naming spaces as well, as it centralizes management and is easy to manage. I'd rate the solution ten out of ten.
It is easy to use the tool. I rate the solution an eight out of ten.
The tool's health check functionality improved our company's service reliability since it is a good feature. Its use still depends on a case-by-case configuration. The tool has certainly fulfilled the basic purpose of monitoring. There is no need to somehow maintain or support the solution. I am not sure how Amazon Route 53 can handle traffic spikes and what difference it has made to our company's service availability. The tool is not difficult to use, and it does what it is meant to do. I rate the tool an eight out of ten.
I would recommend Amazon Route 53 to other users because it can concentrate every configuration on the same platform. Overall, I rate the solution ten out of ten.
We expose DNS to the public, and based on that, we use Amazon Route 53 in our load balancer. Amazon Route 53 provides good traffic management. If we change the IP of any VMs or server to a specific DNS, it gets automatically updated within a time frame and gives a very good exposure to the public. The solution's A record and CNAME record are the most beneficial features for domain registration and management. The solution's health check feature is good because it keeps checking the health of the service. The solution integrates well with other AWS services, load balancers, VMs, or EC2 instances. I would recommend Amazon Route 53 to other users because it is a good tool for traffic flow and DNS mapping. Overall, I rate the solution ten out of ten.
The product can be used for DNS management if a user connects the DNS name with Amazon Route 53. The tool can be used for DNS-related purposes. The product helps our company set up and register domain names. The tool also helps our company to add a domain name address to a website on the browser. The product helps with the traffic flow feature as it allows you to assign CIDR blocks and IP addresses. The tool also helps in the area of DNS queries. The product integrates with other services from AWS, like Amazon S3 bucket and load balancers. The product can also be used with AWS EC2 Instances, AWS Global Accelerator, Amazon SNS, and AWS Lambda. I recommend the product to those who plan to use it. In our company, we use the services of the product without any cloud products. I rate the overall tool an eight out of ten.
For traffic management, the product offers functions similar to other domain name server providers. As an AWS user, having Route 53 as an in-house tool simplifies the entire process, eliminating the need to navigate different platforms for defining the records or other entries. The integration within the AWS ecosystem streamlines the management of DNS services. The most beneficial feature of Route 53 for domain registration, from the engineers' perspective, lies in its seamless integration within the AWS Cloud ecosystem. It becomes easier to manage multiple AWS services in a single platform. The feature for health check efficiently impacts the uptime and reliability of AWS servers including EC2 and EKS. It enables easier traffic routing as compared to GoDaddy. The readiness checks feature ensures that our applications are well-prepared to handle incoming traffic including DNS firewall setup. Also, we can conduct geo-based and latency-based routing. For IT-based routing, they offer a DNS failover feature. I recommend the product to others and rate it a nine out of ten.
It is the first time I did a migration. Overall, I rate the solution a nine out of ten.
I use the latest version of Amazon Route 53. Amazon Route 53 is a cloud-based solution. I would recommend Amazon Route 53 to other users. Overall, I rate Amazon Route 53 a nine out of ten.
Overall, I would rate it nine out of ten.
People using the solution can just enjoy it. It is really fast. Overall, I rate the tool a ten out of ten.
Amazon Route 53 is user-friendly for anyone who knows to work with DNS records. Otherwise, they will have to learn about the different kinds of DNS records. Two people in our company do the solution's configuration. I would ask users to use Amazon Route 53 because I haven't faced any problems with it. Overall, I rate Amazon Route 53 a ten out of ten.
Overall, I rate the solution an eight out of ten.
I would rate the solution an eight out of ten. The product is better than Cloud DNS. You should use Terraform while using Cloudflare so that you do not need to create manually anything. People usually think that they will use Cloudflare less but end up using it more. The best way to go is to follow a pipeline automated process for testing and production.
My advice to others is for them to pay attention to the on-premise integration which can be difficult. I rate Amazon Route 53 a nine out of ten.
The solution is good for configuring load balancers and other items. I rate the solution an eight out of ten.
I would rate Amazon Route 53 a ten out of ten.
I would rate this solution as seven out of ten. Amazon Route 53 is for high availability and scalability. It works well in AWS and handles almost all of the queries. My advice is to use Amazon Route 53, but you need to make sure that it's configured properly because your data and organization could be compromised.