We performed a comparison between Amazon Route 53 and IBM NS1 Connect based on real PeerSpot user reviews.
Find out in this report how the two Managed DNS solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Amazon Route 53 is a DNS resolution service that helps you to map your hostname to another hostname."
"The scalability is the most valuable feature."
"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 initial setup is good and straightforward."
"The solution effectively monitors the health of resources and provides good identity access management."
"The most valuable feature is that it works very well."
"The solution is cost-effective."
"We use Amazon Route 53 for dynamic naming and routing policy."
"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."
"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 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."
"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 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."
"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."
"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."
"The solution’s pricing could be reduced."
"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."
"The product’s security and disaster recovery features need enhancement."
"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."
"There are no detailed logs, and they should implement that in the solution."
"The solution should have a more user-friendly user interface."
"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."
"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 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."
"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."
"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.""
"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."
"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."
Amazon Route 53 is ranked 3rd in Managed DNS with 19 reviews while IBM NS1 Connect is ranked 7th in Managed DNS with 11 reviews. Amazon Route 53 is rated 8.6, while IBM NS1 Connect is rated 9.6. The top reviewer of Amazon Route 53 writes "Provides good DNS mapping, routing, and traffic flow features". On the other hand, the top reviewer of IBM NS1 Connect writes "Balances cost and functionality, speeds up provisioning, and reduces the DNS maintenance work drastically". Amazon Route 53 is most compared with Azure DNS, Cloudflare DNS, Google Cloud DNS, Cisco Umbrella and Neustar UltraDNS, whereas IBM NS1 Connect is most compared with Cloudflare DNS, Akamai Edge DNS, Neustar UltraDNS, Hurricane Electric Free DNS and Azure DNS. See our Amazon Route 53 vs. IBM NS1 Connect 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.