We compared Azure DNS and Amazon Route 53 based on our user's reviews in several parameters.
Azure DNS is praised for its reliability, scalability, and ease of use, with excellent customer service and a favorable ROI. On the other hand, Amazon Route 53 is noted for its excellent DNS management capabilities, performance, integration with AWS, and comprehensive monitoring tools. Users appreciate the competitive pricing structures of both services, but suggest improvements in areas such as uptime, interface simplicity, and documentation.
Features: Azure DNS differentiates itself from Amazon Route 53 with its ease of use, seamless integration with other Azure services, and competitive pricing. On the other hand, Amazon Route 53 offers excellent DNS management capabilities, comprehensive monitoring and alerting tools, and reliable performance.
Pricing and ROI: The setup cost of Azure DNS and Amazon Route 53 differ in their pricing structure and setup simplicity. Azure DNS is highly regarded for its cost-effectiveness and hassle-free setup process, while Amazon Route 53 offers flexible pricing options and a straightforward setup cost., Azure DNS has favorable ROI with cost-effectiveness, efficiency, increased productivity, decreased downtime, and improved performance. Users appreciate easy setup and management. Amazon Route 53 offers positive ROI with reliability, efficiency, and value as a DNS service, as reported by users.
Room for Improvement: Azure DNS users have highlighted areas for improvement in reliability, uptime, and a more user-friendly management interface. They also desire more comprehensive documentation and a simplified pricing structure. On the other hand, Amazon Route 53 could enhance resolving latency issues, user interface, documentation, integration with other AWS services, and advanced features like traffic routing options.
Deployment and customer support: The reviews for Azure DNS and Amazon Route 53 indicate that the duration required for establishing a new tech solution can vary. Some users of Azure DNS spent three months on deployment and an additional week on setup, while for Amazon Route 53, there were mixed reviews with some users taking three months for deployment and an additional week for setup, and others completing both within a week., Azure DNS customer service has been highly praised, with prompt and efficient assistance. Users appreciate the knowledgeable and responsive support staff. Amazon Route 53 also has positive feedback, with prompt and helpful assistance from their support team. Users appreciate their expertise and ability to provide reliable solutions.
The summary above is based on 35 interviews we conducted recently with Azure DNS and Amazon Route 53 users. To access the review's full transcripts, download our report.
"The solution has a user-friendly dashboard."
"The scalability is the most valuable feature."
"Technical support from Amazon is very good...Overall, the product is stable."
"The main DNS resolution is really, really fast."
"We use Amazon Route 53 for dynamic naming and routing policy."
"The product's initial setup phase was very easy."
"The feature for health check efficiently impacts the uptime and reliability of AWS servers including EC2 and EKS."
"The most valuable feature is that it works very well."
"It is a scalable solution."
"The DNS resolution is the most valuable feature."
"The setup is relatively straightforward."
"Data protection is paramount across cloud platforms"
"What I like about Azure DNS is that it doesn't have any issues and integrates quickly with other products. It has good integration, which is incredible. I also like that whenever you deploy private links and endpoints, Azure DNS gives you the option to select the Azure native DNS, private DNS, or go with the Azure custom DNS. It depends, but if you don't have any dependencies on the DNS, then, like many customers, you won't have DNS issues. Azure DNS is a very good solution that helps you with domains and other resources."
"The most valuable feature of Azure DNS is it works automatically after configuration. Additionally, the solution is secure."
"Can be configured to achieve a hundred percent reliability"
"It is a very stable solution."
"It is difficult to manage the product if the person involved in the setup process doesn't know much about the solution."
"When you add a new DNS record instructing the solution to map one thing to another, it has to propagate to all the networks, which takes some time."
"Streamlining and optimizing processes related to Procter, VPN workflows, and other subjects based on specific needs would allow for continual improvement and adaptation to the evolving requirements of the system."
"The multiple routing policies present in the product have certain shortcomings where improvements are required."
"The solution’s pricing and technical support could be improved."
"When we are looking at the model registry, it may be not clear sometimes. For example, if you use a single grid model and group or registry, it has a different SDK in the pilot. And it may be not so comfortable to use both of them because it is two different places for keeping things in order."
"Route 53 would be better if it had the ability to handle multiple requests at the same time because we have a lot of users. I would like that to be optimized in the next version."
"The cost calculator for determining the cost of Route 53 is a little bit obscure."
"The licensing cost should be improved."
"The product must provide information on which DNS or application is consuming the most budget."
"What needs improvement in Azure DNS is visibility in terms of troubleshooting. It's similar to the area for improvement in Azure Network Watcher, where I can see how the source is going out if I'm troubleshooting a source destination. I can also see the destination. As for seeing how the packet travels, that's what should be improved. It's still lacking in visibility. Suppose I'm looking into backend machines, and if I'm hitting another NPM machine or any machine on the other side, there should be visibility. The tool should tell you that a specific machine is passing through a VPN gateway or route table, routing to a third-party firewall, and then dropping. Azure DNS should show an accurate answer to help the customers, which is its area for improvement."
"While it's stable, there's always room for improvement to ensure it remains reliable."
"The product must be integrated with additional security features."
"There are some issues with the solution's performance where improvements are needed."
"The solution should provide better pricing."
"The scalability could improve."
Amazon Route 53 is ranked 3rd in Managed DNS with 19 reviews while Azure DNS is ranked 2nd in Managed DNS with 31 reviews. Amazon Route 53 is rated 8.6, while Azure DNS is rated 8.4. The top reviewer of Amazon Route 53 writes "Provides clear documentation, easy to understand, simplifies management and efficiently handles our domain-related configurations and DNS records". On the other hand, the top reviewer of Azure DNS writes "Offers good performance and helps its users with disaster recovery". Amazon Route 53 is most compared with Cloudflare DNS, Google Cloud DNS, Cisco Umbrella, Akamai Edge DNS and Neustar UltraDNS, whereas Azure DNS is most compared with Cloudflare DNS, Cisco Umbrella, Infoblox DDI, Google Cloud DNS and Quad9. See our Amazon Route 53 vs. Azure DNS report.
See our list of best Managed DNS vendors.
We monitor all Managed DNS reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.