1. Home
  2. Managed DNS Services
  3. Amazon Route 53 Reviews
  4. User Review of Amazon Route 53
No-brainer DNS servers for the AWS Ecosystem, easy to use
September 14, 2020

No-brainer DNS servers for the AWS Ecosystem, easy to use

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Amazon Route 53

As part of our Cloud migration to AWS we have started using Route 53. Being able to programmaticaly build all aspects of the deployment in general and for route 53 in particular is a life saver. Being part of the same ecosystem make deploying so much easier... As we move all on-prem to AWS, and DNS is essential, Route 53 we need to rely on R53 and it delivers.
  • Plain DNS.
  • Easy to programmatically administer.
  • There are a few limitations which we encountered but hope will be resolved soon.
  • Not R53 speficic, but naming conventions are essential.
  • Quicker deployments.
  • Programmatic naming conventions.
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.
Especially the community support is great. Being such a widely used product there are many available option apart from the official AWS support options.
We are using Route 53 purely programmatically via the APIs. This make it very easy for deployments and keep all naming conventions according to policies. Very happy with it.

Do you think Amazon Route 53 delivers good value for the price?

Yes

Are you happy with Amazon Route 53's feature set?

Yes

Did Amazon Route 53 live up to sales and marketing promises?

Yes

Did implementation of Amazon Route 53 go as expected?

Yes

Would you buy Amazon Route 53 again?

Yes

Being in the AWS ecosystem, using Route 53 is more or less a given. There are other options out there but none are as integrated into the ecosystem as Route 53. Especially for your internal name resolving there realistically is no other viable alternative. For external name resolving there are other options out there with more options, but do you really need them.