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

Google Cloud DNS vs IBM NS1 Connect comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Nov 4, 2024

Review summaries and opinions

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

Categories and Ranking

Google Cloud DNS
Ranking in Managed DNS
7th
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
7
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 July 2025, in the Managed DNS category, the mindshare of Google Cloud DNS is 6.6%, up from 5.8% compared to the previous year. The mindshare of IBM NS1 Connect is 1.2%, down from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed DNS
 

Featured Reviews

Shikar Singh - PeerSpot reviewer
Constantly improving and adapting to customer needs
The effectiveness of Google Cloud DNS largely depends on where an organization stands in its cloud journey and its overall technology landscape. For those heavily invested in Google Cloud Platform (GCP) and already embracing cloud solutions, Google Cloud DNS can be rated quite high, ranging from seven to nine out of ten.Deployment times for Google Cloud DNS can vary depending on the complexity of the infrastructure and configuration requirements. For straightforward setups and cloud-ready cases, deployment can typically be completed within a few minutes to an hour. However, in more complex infrastructure scenarios involving extensive configuration, deployment may take longer, possibly spanning days or weeks.
Adam Surak - PeerSpot reviewer
Handles customer-facing records and upstream selection logic with good efficiency
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. If we have about 1,000 endpoints, that translates to around 150,000 records. Assuming there's an even distribution, so every time a server fails or an endpoint goes on a level, we would have 150 updates. With NS1, we have one, so this had an even more significant effect. There are situations where we have thousands of specific records sharing the same responses. In that case, there is one update instead of thousands and thousands. When we chose Managed DNS in 2014, it was the only solution that could do what we wanted, but I'm not sure about the current state of the market. The NS1 API is an API on top of a managed DNS. It's not an afterthought. It's not like the solution existed. Someone was sending updates by email. Then a product manager came along and said, "Hey, there is this cool thing. It's called an API. Maybe we should do it?" And they are like, "Okay. Let's do it." In the case of NS1, they thought about how to use an API to manipulate and retrieve the stuff. It's supposed to be API-driven. Also, NS1 doesn't have hidden features that would not be available over the API. Even their dashboard is built on top of the API. You can leverage all the functionality programmatically. That's what we do. We don't use their native integrations because we have been customers before these integrations and real-time telemetry existed. Our solution isn't leveraging either of those. Instead, we leveraged their API integration, which was the first thing that existed. Indeed, the API is at the core of how we use Managed DNS. No one goes to the dashboard or manually clicks anything. Everything goes via the API, and we perform hundreds of changes every minute. The API automatically drives everything, so that's the integration we leverage. We don't use the Pulsar Active Steering feature because we don't have a website. Our solution is being used as an API for other solutions. You can put the Pulsar agent on the website and feed NS1 the information. In our case, we are integrating into third-party sites. We cannot put our JavaScript on their websites for NS1 to provide the data, so we don't.

Quotes from Members

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

Pros

"Google Cloud DNS continues to evolve based on customer feedback and technological advancements."
"The initial setup process is easy."
"The most significant features are the internal and external endpoints using Google Cloud DNS, which are very beneficial for dependent apps."
"It is a scalable solution."
"The scalability is good."
"The tool is well integrated. We don’t need the interface of another provider. The product helps me manage my domain and write in Google Cloud."
"Stability-wise, I rate the solution a ten out of ten."
"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."
"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."
"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 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."
"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."
"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."
"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."
 

Cons

"The cost of using Google Cloud DNS can be relatively high compared to other options, especially considering the cloud environment."
"It needs to provide better integration."
"The solution's price could be better."
"Migrating away from Google Cloud DNS can be difficult."
"The UX of the product is an area with certain shortcomings where improvements are required."
"The UI is tricky to understand for people who have not worked with DNS records. People with little to no experience with DNS records can find it hard to understand. For example, you need to know the hallmarks to input records since they need to be matched in a specific format."
"More features around rules-based configurations would be beneficial."
"There could maybe be additional ways to manage traffic. There are no major improvements we're looking for. It's a very complete solution."
"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 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."
"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."
"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."
"We would really like them to become a DNS registrar."
 

Pricing and Cost Advice

"The product is expensive."
"The cost of using Google Cloud DNS can be relatively high compared to other options, especially considering the cloud environment. I would rate it 6 out of 10. Cheaper alternatives might be desirable, but the decision depends on various factors such as vendor lock-in, organizational adaptability, and alignment with other technologies in use."
"It is expensive but cost-effective."
"I am not sure about the pricing. However, I can give you a rough estimate which is like ten cents per month per zone."
"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."
"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."
"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."
"The cost of this product is one of the reasons that we chose it."
report
Use our free recommendation engine to learn which Managed DNS solutions are best for your needs.
863,641 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Comms Service Provider
13%
Educational Organization
7%
Manufacturing Company
7%
Computer Software Company
14%
Comms Service Provider
11%
Financial Services Firm
9%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Google Cloud DNS?
Google Cloud DNS continues to evolve based on customer feedback and technological advancements.
What is your experience regarding pricing and costs for Google Cloud DNS?
Pricing and support are really good. There are no complaints about the pricing.
What needs improvement with Google Cloud DNS?
I am not heavily involved with Cloud DNS, but from an end-user perspective, the customization part could be improved. More features around rules-based configurations would be beneficial.
Ask a question
Earn 20 points
 

Also Known As

No data available
NS1 Managed DNS, NS1
 

Overview

 

Sample Customers

MeilleursAgents
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 Google Cloud DNS vs. IBM NS1 Connect and other solutions. Updated: July 2025.
863,641 professionals have used our research since 2012.