Amazon Route 53 vs Azure DNS comparison

Sponsored
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 6, 2024
 

Categories and Ranking

IBM NS1 Connect
Sponsored
Ranking in Managed DNS
7th
Average Rating
9.6
Number of Reviews
11
Ranking in other categories
No ranking in other categories
Amazon Route 53
Ranking in Managed DNS
3rd
Average Rating
8.8
Number of Reviews
20
Ranking in other categories
No ranking in other categories
Azure DNS
Ranking in Managed DNS
2nd
Average Rating
8.4
Number of Reviews
31
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2024, in the Managed DNS category, the mindshare of IBM NS1 Connect is 3.5%, down from 3.5% compared to the previous year. The mindshare of Amazon Route 53 is 22.8%, down from 25.5% compared to the previous year. The mindshare of Azure DNS is 21.4%, down from 24.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed DNS
Unique Categories:
No other categories found
No other categories found
No other categories found
 

Featured Reviews

Valentino Volonghi - PeerSpot reviewer
Feb 15, 2022
Terraform integration means all entries are created and Configuration done at deploy time, reducing manual work
We use the geo load balancing functionality and there are a couple of things that are helpful there. But the language itself is something we had to get used to a little bit. Some of my folks made a few mistakes in rolling out the Filter Chain. It doesn't return all of the multiple results by default. It returns only one. So we have to add a bunch of operations, like geo-target by first selecting a group in terms of regional proximity and then shuffle the list of potential endpoints and then select the first one. The Filter Chain setup is a bit hard to grasp at first. It would also be nice to have a way to simulate changes in addition to staging. Also, right now, as far as I understand, there is no way to do atomic changes to a DNS configuration. You need to make changes record by record and apply. But if someone wants to do more complex stuff like, for example, if I want to migrate from a CNAME to an A record being served, or vice versa, that's typically something that involves first taking out all of the CNAMEs and then adding all of the A records. That would require some downtime. It would be a lot easier if I could just have the new full record with the CNAME or A record, and then be able to replace the nodes directly in a single operation and I don't think they have that.
Bireshwar Adhikary - PeerSpot reviewer
Jan 20, 2023
Effective for processing domain registrations and configuring load balancers
Our company uses the solution for DNS services. We purchase domains, create load balancers, set provisions, host websites, and manage how internet traffic routes to websites. The solution handles all DNS queries and translates friendly domain names to numeric IP addresses.  It is easy to process…
Bruno Clemente - PeerSpot reviewer
Nov 1, 2023
A stable solution that saves us time and cost and provides excellent integration features
We use the solution for some e-commerce sites that we use. It also integrates with our Kubernetes environment on Azure Azure DNS improves our integration with the Kubernetes environment. When we scale or increase our Kubernetes site, the tool updates DNS automatically. It saves us time and cost.…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Monitoring is really important for us. We really care about reliability, and we want to make sure that we can remove some points of presence in our sector and in our edge network really fast when we experience any problems. So, monitoring that NS1 provides for DNS is really important for us."
"We find that the low latency access to DNS queries has a direct effect on the customer experience. Visiting a site, whether it's an AdTech-based solution or marketing tech, the fact that whatever we're rendering on a page can be rendered better than the industry standard, in terms of time, ensures a better user experience."
"Everything we download into our observability platform so that we can also track any changes in traffic behavior or things like that is also something that we use quite a lot. I'd say traffic management, the speed of updates, and observability are the top three things that we use."
"The Filter Chain is one of the most valuable features, for geo-load balancing and geo-fencing. The Filter Chain is the most useful because it allows us to do several things. With geo-fencing we can redirect a particular user to a particular answer. That's very valuable for us. Filter Chains with monitoring is our strategy to provide redundancy."
"For starters, it integrates with Terraform and a lot of our infrastructure is effectively built out using Terraform. That makes all this stuff extremely easy... when we deploy, all the entries are created and configuration is done."
"Their Pulsar filters allow us to collect RUM metrics from our users so that we can determine the best paths for our users to take. That has been very useful in providing the best user experience, and for responding to and recovering from downtime of our multiple CDNs."
"The fact that it's an API-first platform for DNS and application traffic management is one of the reasons we looked into NS1. We use it for a lot of automation and metrics gathering and it's been great."
"We leverage two things from Managed DNS that we couldn't do with any other solution. One is their filter chain technology, which allows us to shift some of the intelligence we need for the traffic steering to the DNS. The second one is data sources, which enables us to manipulate multiple records simultaneously using NS1's internal message DOS. In our case, we are trying to direct the traffic in over 150,000 different NS1 records to an arbitrary set of repeating responses."
"Technical support from Amazon is very good...Overall, the product is stable."
"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."
"The solution has a user-friendly dashboard."
"The scalability is the most valuable feature."
"The solution offers you the flexibility to control configuration rules."
"The initial setup is good and straightforward."
"Amazon Route 53 is a DNS resolution service that helps you to map your hostname to another hostname."
"The product's initial setup phase was very easy."
"The integration with other services on Azure is valuable."
"From a security perspective, Microsoft is much better than other cloud providers."
"The most valuable features of Azure DNS are the DNS forwarder and the DNS additional record editions."
"We use the solution to host IP addresses, sites like microsites."
"The solution allows you to host DNS service without using Azure's servers."
"The initial setup is straightforward and not that complex."
"The best feature is the domain register. The other great feature is that whenever you create any resources, Azure DNS will automatically create a record for you."
"The most valuable feature of the solution is that it is a stable product."
 

Cons

"I would love to see improvement in the testing capabilities they provide. They have a simulate-filter feature so that you can simulate how your traffic would flow, based on their Filter Chains. I believe that was shut off for quite some time. Having that as a way to test our load-balanced CDN structure would be fantastic."
"We use our client in our infrastructure to communicate with NS1. This client is a bit complex in the way that it is set up. NS1 has their own client solution that you can deploy into your platform to do this, but even that is a bit complex. So, I would like a very simple, thin, light API agent that we can deploy into our platform to communicate with NS1. That would be welcome."
"We care about monitoring and telemetry work, and NS1 provides a pretty good system for monitoring. We can monitor our endpoints and points of presence around the world. If there are any issues, we can easily remove them from our network, but this area needs some improvement because it is not always reliable in NS1. In the past, we had a number of false-positive cases when the monitoring system told us about some problems in our infrastructure that were not true. NS1 is improving the system, and we are constantly talking about this with them. I know that they are releasing a new version of their monitoring system, which is really important for us, but this is a different area where we would expect them to improve."
"There could maybe be additional ways to manage traffic. There are no major improvements we're looking for. It's a very complete solution."
"The reporting metrics are great from an API standpoint, but it would be a little bit nicer if there was some type of dashboard around that. There should also be some type of reporting that's more executive-level focused."
"I would like to see the UI updated to allow me to do finer searches. I would also like to have the ability to get reports that can sort based on various metrics. For example, I would like to be able to say, "Show me the top 10 records by total queries" in an easy-to-digest format."
"We use the geo load balancing functionality and there are a couple of things that are helpful there. But the language itself is something we had to get used to a little bit. Some of my folks made a few mistakes in rolling out the Filter Chain...The Filter Chain setup is a bit hard to grasp at first. It would also be nice to have a way to simulate changes in addition to staging."
"The Filter Chain simulation is really good in the UI, but it would be nice to have something similar in the API so that we could simulate and test things before we deploy them."
"The solution’s pricing and technical support could be improved."
"The cost calculator for determining the cost of Route 53 is a little bit obscure."
"The multiple routing policies present in the product have certain shortcomings where improvements are required."
"It is difficult to manage the product if the person involved in the setup process doesn't know much about the solution."
"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."
"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."
"Supporting DNS check is one feature missing in the solution."
"The product could improve its price."
"Azure DNS sticks mostly with the Azure native solution and doesn't scale well in a multi-cloud or hybrid environment."
"The security features and stability needs to be bettered."
"The initial setup of this solution could be less complex and require less manual configurations."
"The technical support can be more knowledgeable."
"Azure DNS' documentation needs to improve."
"The product must provide information on which DNS or application is consuming the most budget."
"I would like to see more security features and protection."
"The CDN integration could be improved."
 

Pricing and Cost Advice

"Everything can always be cheaper, but as it is today the pricing is fair."
"NS1's pricing is much more aggressive than its competitors in the market and you get more value out of what you pay for it."
"We pay about $30,000 a month. We used to pay about $20,000 with Dyn every month, for lower volume than we're doing right now, but it had none of the features that we have available with NS1, so it was worth it for us. It seems competitive for us, given that we're doing 4.5 billion requests."
"From a cost standpoint, it's certainly not the most expensive out there, and it's also not the cheapest, but it does well to balance the cost and the functionality/reliability."
"The cost of this product is one of the reasons that we chose it."
"We pay per use."
"The price of Amazon Route 53 is reasonable."
"The price of the solution could be a little bit lower compared to Google DNS, which has more features than Amazon."
"Amazon Route 53 is not an expensive solution."
"It can be expensive compared to some other providers."
"Amazon Route 53 is an expensive solution."
"The price of the product is perfectly fine in my opinion."
"Amazon Route 53 is not that expensive."
"The solution is free."
"In my opinion, DNS is inexpensive. The pricing depends on how you use it, but overall, it's quite affordable. It typically costs just a fesw cents, and Microsoft even offers ten thousand free hits per month."
"Azure DNS is a cheap solution, and I rate it a two out of ten for pricing."
"I would describe Azure DNS as a cheaply priced product."
"We have an enterprise license agreement with Microsoft. Their pricing is competitive. I would rate it a three and a half out of five."
"The solution payment model is based on how many users use it. This is not an expensive solution, but it can depend on how long we use it. However, if the price was decreased it would be helpful."
"We use the tool's free version."
"The solution is moderately priced."
report
Use our free recommendation engine to learn which Managed DNS solutions are best for your needs.
793,295 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
22%
Financial Services Firm
14%
University
9%
Comms Service Provider
6%
Educational Organization
21%
Computer Software Company
15%
Financial Services Firm
9%
Manufacturing Company
7%
Computer Software Company
17%
Financial Services Firm
10%
Manufacturing Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about NS1 Managed DNS?
For starters, Managed DNS from NS1 is an easy way to get the job done. Whether you're a novice or a pro, Managed DNS ...
Azure DNS or Amazon Route 53?
Azure DNS is a hosting service of DNS domains. It has excellent operating time and performance, resulting in fast res...
What do you like most about Amazon Route 53?
The most valuable features of the solution are the DNS, routing, and traffic features.
What needs improvement with Amazon Route 53?
Since DNS is based on internet access, improving some security features would improve internet quality worldwide.
What do you like most about Azure DNS?
The tool is easy to manage and use.
What needs improvement with Azure DNS?
The web interface to manage the solution must be made easier. The tool must provide seamless integration between DHCP...
What is your primary use case for Azure DNS?
We use the solution for domains. We manage the name servers using the tool.
 

Also Known As

NS1 Managed DNS, NS1
Route 53
No data available
 

Overview

 

Sample Customers

Avast Software, Bloomberg L.P., BBC, Carfax, CNBC LLC, Deloitte Consulting LLP, Disney Streaming, Dropbox, EBAY Inc, Gannett Media Corp, Salesforce, Wayfair, Workday
Hess, Expedia, Kelloggs, Philips, HyperTrack
M-Files
Find out what your peers are saying about Amazon Route 53 vs. Azure DNS and other solutions. Updated: July 2024.
793,295 professionals have used our research since 2012.