We performed a comparison between Azure DNS 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."The most valuable feature of the solution is that it is a stable product."
"We use the solution to host IP addresses, sites like microsites."
"The setup is relatively straightforward."
"It is a scalable solution."
"Azure DNS provides value beyond its user-friendly interface and easy learning curve."
"It is a scalable solution."
"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 the simplicity of putting DBs."
"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."
"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."
"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."
"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."
"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."
"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."
"While it's stable, there's always room for improvement to ensure it remains reliable."
"There are issues with the cloud systems."
"I would like to see more security features and protection."
"The web interface to manage the solution must be made easier."
"Azure DNS does provide enhanced support for applications and includes several security features to protect against threats. One of the security features it offers is the ability to detect and prevent dangling DNS records, which can be used in cyber attacks. Dangling DNS records occur when a website owner creates a domain name but forgets to remove the CNAME record, leaving the domain vulnerable to takeover by malicious actors. Azure DNS includes security measures to identify and prevent such threats, helping to keep your DNS infrastructure secure. However, if Microsoft could add more security capabilities to the DNS, that would be great to detect and identify anomalies that are happening to prevent cyber threats."
"There are some latency issues that could be improved."
"The security features and stability needs to be bettered."
"Azure DNS sticks mostly with the Azure native solution and doesn't scale well in a multi-cloud or hybrid environment."
"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 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."
"We would really like them to become a DNS registrar."
"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."
"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."
"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."
"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 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."
Azure DNS is ranked 2nd in Managed DNS with 31 reviews while IBM NS1 Connect is ranked 7th in Managed DNS with 11 reviews. Azure DNS is rated 8.4, while IBM NS1 Connect is rated 9.6. The top reviewer of Azure DNS writes "Offers good performance and helps its users with disaster recovery". 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". Azure DNS is most compared with Amazon Route 53, Cloudflare DNS, Cisco Umbrella and Infoblox DDI, whereas IBM NS1 Connect is most compared with Cloudflare DNS, Akamai Edge DNS, Amazon Route 53, Neustar UltraDNS and Infoblox DDI. See our Azure DNS 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.