Try our new research platform with insights from 80,000+ expert users

Amazon Route 53 vs IBM NS1 Connect comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Nov 4, 2024
 

Categories and Ranking

Amazon Route 53
Ranking in Managed DNS
2nd
Average Rating
8.8
Reviews Sentiment
7.3
Number of Reviews
31
Ranking in other categories
No ranking in other categories
IBM NS1 Connect
Ranking in Managed DNS
12th
Average Rating
9.6
Reviews Sentiment
8.0
Number of Reviews
11
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of December 2024, in the Managed DNS category, the mindshare of Amazon Route 53 is 20.7%, down from 24.1% compared to the previous year. The mindshare of IBM NS1 Connect is 2.7%, down from 3.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed DNS
 

Featured Reviews

Jithin Scaria - PeerSpot reviewer
Provides clear documentation, easy to understand, simplifies management and efficiently handles our domain-related configurations and DNS records
For initial setup, we generally use provisioning tools for these kinds of DNS records. The choice often depends on the cloud provider and the Infrastructure as Code (IAC) tools the client prefers. We adapt our approach accordingly rather than focusing on a single method within Route 53. The documentation is very user-friendly. Even someone with no prior experience can easily understand it. It provides step-by-step instructions and explains things in a clear and concise way. You can find everything you need to know about Route 53 and its features in the documentation, including white papers. In addition to manual configuration, you can also use third-party tools like Terraform, Pulumi, or AWS CloudFormation templates to manage your Route 53 configurations.
Michael Wills - PeerSpot reviewer
Balances cost and functionality, speeds up provisioning, and reduces the DNS maintenance work drastically
The provisioning is great. They have an API service that is simple to use and very quick. The changes that we make are replicated worldwide in a matter of usually milliseconds, sometimes seconds. They are done very rapidly. That's something that's obviously priceless when we're dealing with things like DNS. It is great as an API-first platform for DNS and application traffic management. It is very simple to use. It allows us to rapidly provision and deprovision things. We are all around happy with the solution. From a metrics standpoint, the solution that we came from had no metrics. So, it has been great. Their service team is excellent in taking the time to provide reports for both growth and strategic planning. It has been great.

Quotes from Members

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

Pros

"Amazon Route 53 is easy to manage and install."
"The solution effectively monitors the health of resources and provides good identity access management."
"The scalability is the most valuable feature."
"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 tool's most valuable feature is in the area of domain registration and routing DNS."
"You can host your zone and name servers here, and keeping track of records is easy."
"The solution is stable."
"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."
"One of the features that is non-standard and that is very useful is the filtered DNS. We have set up our external VPN, which is what all our employees connect through, to use this feature. It's geolocation-aware. In that way, for India we set it up so that these are the servers that should be supporting things, and in the UK these servers, in the U.S. these servers, and in Sweden these ones."
"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 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."
"It massively speeds things up. Today, we allow developers to deploy services and have externally facing DNS scrapers that are created automatically without the addition of human intervention."
"The provisioning is great. They have an API service that is simple to use and very quick. The changes that we make are replicated worldwide in a matter of usually milliseconds, sometimes seconds. They are done very rapidly. That's something that's obviously priceless when we're dealing with things like DNS."
"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."
"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."
 

Cons

"Supporting DNS check is one feature missing in the solution."
"There isn't room for recommending new configurations."
"The solution’s pricing could be reduced."
"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."
"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."
"The solution’s pricing and technical support could be improved."
"The number of domain types available on AWS, such as the .br domain for Brazil, should be expanded."
"The solution should include more robust and secure services for hardening sites."
"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."
"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."
"When we first deployed, we flipped the switch, and it didn't work as well as we expected. It wasn't a complete outage, but we had issues in some places with some customers. The NS1 team went out of their way to resolve it on Thanksgiving. We have a post about it on our blog. We called it "Black Thursday.""
"We would really like them to become a DNS registrar."
"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 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."
"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."
 

Pricing and Cost Advice

"The price of the solution could be a little bit lower compared to Google DNS, which has more features than Amazon."
"The tool is a bit expensive."
"Amazon Route 53 is not that expensive."
"Amazon Route 53 is not an expensive solution."
"The pricing depends on usage and is moderate."
"We pay per use."
"Amazon Route 53 is an expensive solution."
"It can be expensive compared to some other providers."
"The cost of this product is one of the reasons that we chose it."
"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."
"Everything can always be cheaper, but as it is today the pricing is fair."
"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."
"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."
report
Use our free recommendation engine to learn which Managed DNS solutions are best for your needs.
824,053 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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 resolution. We like the ability to view everything in the Azure portal - this makes...
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?
In my project, everything is already configured, and we focus on monitoring and health checks. There isn't room for recommending new configurations. However, the initial setup isn't something we ar...
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 Providers provide all of the tools necessary for efficient and reliable DNS mana...
 

Also Known As

Route 53
NS1 Managed DNS, NS1
 

Overview

 

Sample Customers

Hess, Expedia, Kelloggs, Philips, HyperTrack
Avast Software, Bloomberg L.P., BBC, Carfax, CNBC LLC, Deloitte Consulting LLP, Disney Streaming, Dropbox, EBAY Inc, Gannett Media Corp, Salesforce, Wayfair, Workday
Find out what your peers are saying about Amazon Route 53 vs. IBM NS1 Connect and other solutions. Updated: December 2024.
824,053 professionals have used our research since 2012.