We performed a comparison between Cloudflare 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."Its most significant benefit to date is the speed with which it refreshes DNS records on the internet once you change it. If you are changing a website or registering a new record, it is very quick."
"The solution is stable, and the DNS servers are simple to use."
"Cloudflare DNS is widely used, and it's good for websites. If we use Cloudflare DNS and update one record, it updates in their office instantly."
"I get a lot of value from Cloudflare's API because it enables you to build a separate environment inside the solution. You can create a domain for performing test requests before you move to the production environment and connect various domains."
"Even when there is a high load on our servers, Cloudflare is able to cache the data and serve it to users, ensuring they can still access the website."
"The most valuable feature of the solution is external DNS. It is also very secure. They have their own main server and once you configure it, the product takes care of everything. There are no issues in resolving IPs and low latency is also present."
"The most valuable feature of Cloudflare DNS is its global reach and it is always evolving."
"The attacker won't have details since my public IP is anonymous. It offers us good privacy."
"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 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."
"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."
"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."
"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."
"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."
"An integrated SSO feature would be useful for Cloudflare DNS."
"It would be helpful if the solution could continue evolving to compete with the other solutions on the market."
"Cloudflare doesn't have a reverse lookup. We can only do a DNS lookup to get the IP address from the hostname. It doesn't work if you want to look up the hostname from an IPA address."
"The solution could be more user-friendly."
"Cloudflare should add more documentation and pricing to the cloud version."
"The documentation could improve for Cloudflare DNS."
"Cloudflare's free plan is limited to 5,000 records for their free plan. They should increase that. For example, if I create a domain called abc.com and a subdomain called a.abc.com, my record count will be two. I can make a maximum of 5,000 subdomains. However, if we use our own DNS hosted on another provider, there is no limit. Their free plan also lacks name server customization."
"We have noticed multiple instances where Cloudflare falsely indicates that our servers are down, even when there is no actual load on them. This makes it challenging for us to identify the exact issue."
"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 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.""
"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 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 would really like them to become a DNS registrar."
"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."
Cloudflare DNS is ranked 1st in Managed DNS with 13 reviews while IBM NS1 Connect is ranked 7th in Managed DNS with 11 reviews. Cloudflare DNS is rated 8.6, while IBM NS1 Connect is rated 9.6. The top reviewer of Cloudflare DNS writes "A tool that offers good performance that needs to improve in areas like assessment and payload". 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". Cloudflare DNS is most compared with Quad9, Azure DNS, Google Cloud DNS, Cisco Umbrella and No-IP Managed DNS, whereas IBM NS1 Connect is most compared with Akamai Edge DNS, Amazon Route 53, Neustar UltraDNS, Hurricane Electric Free DNS and Azure DNS. See our Cloudflare 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.