Amazon Route 53 Reviews

I use the solution in my company to create or set up DNS for some projects.

The most valuable feature of the solution stems from its ability to help our company in the area of top-level domains, specifically generic top-level domains, and geographic top-level domains, which helps resolve DNS queries and use the hosted zone, which allows us to adjust the DNS part.

It is difficult to manage the product if the person involved in the setup process doesn't know much about the solution. From an improvement perspective, the product should be easy for everyone to understand.

I have experience with Amazon Route 53. I am a customer of the tool.

Stability-wise, I rate the solution an eight out of ten.

Scalability-wise, I rate the solution an eight out of ten.

For the web applications, the employees in our company need Amazon Route 53 to deal with the area of DNS. The product helps users assign the DNS to a particular IP address.

The product's initial setup phase was easy. The product is easy to manage for those who know about the product.

The price of the product is perfectly fine in my opinion.

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.

We are using Amazon Route 53 for DNS management.

Using Amazon Route 53 is located in a central place in Amazon AWS which makes it easier to manage every DNS entry in one place. You are able to manage your public and private DNS from there. We can create rules based on weight and globalization is impressive.

It may not always be easy to integrate with on-premise infrastructure, especially with the complexity of the resolver and other factors involved. Improvements could be made to enhance the ability to integrate seamlessly.

I have been using Amazon Route 53 for approximately three years.

The support of the solution is good.

I rate the stability of Amazon Route 53 a ten out of ten.

The scalability of Amazon Route 53 is wonderful.

We plan to increase our usage of the solution.

I rate the scalability of Amazon Route 53 a ten out of ten.

The support is great.

I rate the support of Amazon Route 53 a nine out of ten.

Positive

We were using a server with DNS and Active Directory.

The initial setup of Amazon Route 53 is easy.

We used one person for the deployment of the solution.

I have received an ROI of the solution.

The price of Amazon Route 53 is reasonable.

I rate the price of Amazon Route 53 an eight out of ten.

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 product is a DNS service for AWS. It manages my DNS resolutions on the internet.

I used to use a free DNS service. I stopped using that, and I bought Amazon Route 53. It has been six years. I have had no problem so far.

The main DNS resolution is really, really fast. I live in Brazil. Most of my infrastructure is in Brazil. If I want my content to be reachable only to Brazilian servers or people using a VPN in Brazil, I can do that using the solution. It’s a really powerful tool.

The product could improve its price.

I have been using the solution for six years. I am using the latest version of the solution.

I never had a downtime.

The product’s scalability is perfect.

The support depends on the tier that we have.

Positive

The initial setup was pretty straightforward.

We see a 100% return on investment in the product.

The product is really cheap. It cost me $1.

People using the solution can just enjoy it. It is really fast. Overall, I rate the tool a ten out of ten.

Its integration with other Amazon services is a very useful feature, in my opinion. It goes well with other Amazon services. So, when we are using other Amazon services, like customer infrastructure on an Amazon cloud, we prefer to use Amazon Route 53.

Supporting DNS check is one feature missing in the solution. The DNS check support is not there in Amazon Route 53. The aforementioned details can be considered for improvement.

Though we don't use Amazon Route 53 regularly, we use it for a couple of projects. So, it has been running for five years. My company has a partnership with Amazon.

Overall, the product is stable.

There are no such issues with the product's scalability.

Technical support from Amazon is very good, especially for those having a business support plan who get instant support. I rate the technical support a nine out of ten.

Positive

The product was also easy to deploy.

The price of the solution could be a little bit lower compared to Google DNS, which has more features than Amazon.

Overall, I rate the solution an eight out of ten.

We use Amazon Route 53 for dynamic naming and routing policy.

The solution should have a more user-friendly user interface.

I have been using Amazon Route 53 for three to four years.

Amazon Route 53 is a stable solution.

Amazon Route 53 is a scalable solution.

The solution’s initial setup is easy.

We implemented the solution through an in-house team. The solution's deployment took around 10 to 15 minutes.

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 a DNS resolution service that helps you to map your hostname to another hostname. We use it to provide custom domain names for all our AWS services that come with a cryptic URL.

I have been using Amazon Route 53 for more than one year.

Amazon Route 53 is a stable solution.

Amazon Route 53 is a scalable solution.

Amazon Route 53's initial setup is easy.

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.

We use the product for DNS load balancing and WAF. 

The solution offers you the flexibility to control configuration rules. 

The product should improve its automation. 

I have been working the product for two years and a half. 

I would rate the solution's stability a ten out of ten. It never went down for me. 

I would rate the tool's scalability a ten out of ten since I didn't have any problems with it. 

The product's setup is straightforward. 

We have got ROI with the tool's use since it prevented us from downtime and losing millions. 

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. 

We use Amazon Route 53 primarily for routing purposes when trying to route to different environments.

During migration, if you want requests to move towards on-premises versus when you're trying to have DNS resolution done on cloud, the features in Route 53 are really good. We also love the health check features.

There are no detailed logs, and they should implement that in the solution.

We have been using this solution for quite some time.

It is a stable solution. However, I haven't used the solution extensively in the production environment, and we have not bombarded it with the load to see the results.

It is scalable. 

The initial setup is good and straightforward.

I rate the solution an eight out of ten. It is a pretty good solution. Genesys routing also plays a significant role, so I think this should be part of the solution.