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."You can host your zone and name servers here, and keeping track of records is easy."
"It stands out for its user-friendly interface, seamless integration with other AWS services, and ability to efficiently manage DNS, making it a valuable tool for various deployment scenarios, including those involving Kubernetes on AWS."
"The solution effectively monitors the health of resources and provides good identity access management."
"The solution has a user-friendly dashboard."
"The product's initial setup phase was very easy."
"We haven't faced any outages or issues directly related to Route 53. It has been 100% stable for me."
"The scalability is the most valuable feature."
"We use Amazon Route 53 for dynamic naming and routing policy."
"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."
"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."
"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."
"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."
"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."
"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."
"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."
"The solution should include more robust and secure services for hardening sites."
"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."
"Supporting DNS check is one feature missing in the solution."
"The solution should have a more user-friendly user interface."
"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 platform is more complicated to learn than one of its competitors."
"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 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 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."
"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."
"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.""
"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."
"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 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."
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 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 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 Infoblox DDI, 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.
