Google Cloud DNS offers seamless integration, performance, and stability, making it easy to manage domains with both internal and external endpoints, essential for various applications.
| Product | Mindshare (%) |
|---|---|
| Google Cloud DNS | 4.8% |
| Cloudflare | 25.9% |
| Quad9 | 23.9% |
| Other | 45.400000000000006% |
| Type | Title | Date | |
|---|---|---|---|
| Category | Managed DNS | Jun 23, 2026 | Download |
| Product | Reviews, tips, and advice from real users | Jun 23, 2026 | Download |
| Comparison | Google Cloud DNS vs Cloudflare | Jun 23, 2026 | Download |
| Comparison | Google Cloud DNS vs Amazon Route 53 | Jun 23, 2026 | Download |
| Comparison | Google Cloud DNS vs BlueCat Integrity | Jun 23, 2026 | Download |
| Title | Rating | Mindshare | Recommending | |
|---|---|---|---|---|
| Cloudflare | 4.3 | 25.9% | 96% | 79 interviewsAdd to research |
| Quad9 | 3.0 | 23.9% | 50% | 2 interviewsAdd to research |
| Company Size | Count |
|---|---|
| Small Business | 2 |
| Midsize Enterprise | 1 |
| Large Enterprise | 4 |
| Company Size | Count |
|---|---|
| Small Business | 82 |
| Midsize Enterprise | 59 |
| Large Enterprise | 122 |
Google Cloud DNS provides robust performance in managing domains. With user-friendly features for DNS zones and application-specific DNS assignments, it supports both internal and external endpoints, enhancing application performance. Known for quick reflection and technical support, it operates reliably across different cloud platforms, crucial for load balancing and web applications. Users note that improvements in UX and documentation could facilitate more effective use, especially for those less familiar with DNS records. Integration challenges, particularly with Cloudflare, and migration issues are areas for enhancement. While cost concerns exist compared to cheaper providers, users desire improved customization and rules-based configurations.
What are the key features of Google Cloud DNS?Industries primarily use Google Cloud DNS for server management and domain publication. It serves as both public and private domain solutions in network architectures like hub-and-spoke setups. Organizations leverage it for applications reliant on Google Kubernetes Engine or Google Compute Engine with load balancers. It manages traffic effectively across network setups, allowing infrastructure changes without affecting application availability. For many, it is the default choice for DNS services.
MeilleursAgents
| Author info | Rating | Review Summary |
|---|---|---|
| Solutions Architect / IT Program Manager at Optum | 4.0 | In my experience, Google Cloud DNS is crucial for network architecture, especially with its traffic management capabilities across various setups. Although constantly evolving, it remains reliable for web applications and adaptable across multiple cloud providers to meet customer needs. |
| Engineering Manager at a tech services company with 10,001+ employees | 4.0 | I use Google Cloud DNS for my app running on GKE or GCE with internal and external load balancers. While it suits pricing needs over AWS, improvements in customization and rules-based configurations could enhance its value for dependent apps. |
| Team Lead- Sr. Linux administrator-Kubernetes-DevOps at ExpressRCM | 4.0 | Google Cloud DNS is user-friendly, allowing easy DNS zone creation and technical support. However, migrating away and integrating with Cloudflare is challenging, and it's more expensive compared to other providers. Overall, the quick reflection feature is beneficial. |
| Solutions Architect at CGI | 4.0 | I use Google Cloud DNS as our main server for managing public and private domains. It's well-integrated, eliminating the need for another provider's interface. However, the UI can be challenging without DNS record experience and lacks detailed UX guidance. |
| Senior FullStack Developer/Engineer/Architect at Capitbrok | 4.5 | Google Cloud DNS is user-friendly, offering good stability and integration with cloud platforms. While the pricing could be improved, it delivers a return on investment. I have not considered or used alternative solutions. |
| DevOps Engineer at Digified | 4.5 | We primarily use Google Cloud DNS for managing DNS servers and publishing domains. It's fast, easy to set up, stable, and scalable. However, better integration, especially with VMs, and improved documentation are needed. We haven't considered alternative solutions. |
| CTO Cloud Access & Network Security at a tech vendor with 1,001-5,000 employees | 4.5 | I use Google Cloud DNS as a default DNS service, but my company still prefers AWS for DNS needs due to its integration into our existing AWS cloud services. However, Google Cloud DNS's UX could use some improvements. |
In the network architecture, the implementation of Google Cloud DNS varies based on specific needs. For example, in a hub-and-spoke setup along with firewalls and other configurations, DNS is configured as needed.
Traffic management solutions with Google Cloud DNS include both inbound and outbound traffic management across various network setups, such as shared or dedicated virtual private clouds.
Generally, the choice will depend on the traffic focus and the need for load balancing. Regarding reliability, Google Cloud DNS plays a crucial role in web-based applications and can impact services significantly. However, DNS is not exclusive to Google Cloud and can be used across various cloud providers, making its configuration essential for overall service reliability.
Google Cloud's backend network infrastructure is constantly improving and adapting to customer needs. They lead innovation within the cloud-native space, with products like Kubernetes and other solutions developed by Google. These innovations aim to address customer requirements, enhance security, streamline service delivery, and accelerate time-to-market. While I may not have extensive technical knowledge in networking, Google Cloud DNS continues to evolve based on customer feedback and technological advancements.
I have been using Google Cloud DNS for the past 4 years.
I would rate stability around seven out of ten, with factors such as topology and organizational infrastructure influencing the rating.
Scalability with Google Cloud DNS is exceptionally high, typically rated between eight to nine out of ten.
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.
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.
Google Cloud DNS is a great solution, especially for networking needs within Google's ecosystem. I find it to be quite impressive, not just for DNS but for various networking aspects. Based on my experience, I would definitely recommend it to others.
I have my app, which is running on either GKE or GCE. We have a load balancer. We use both internal and external load balancers. If we want to change the underlying infrastructure, like in different regions, without impacting the front-end apps, we use the applications with Google Cloud DNS.
I haven't thought about cost savings or operational improvements specifically attributed to Google Cloud DNS.
The most significant features are the internal and external endpoints using Google Cloud DNS, which are very beneficial for dependent apps.
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.
We have been using Google Cloud DNS for the last two to three years.
Google Cloud DNS is very stable. I have never seen any problems or issues.
Google Cloud DNS is very scalable. I would rate its scalability between eight and nine.
Google's technical support is very responsive and quick. The moment you open a case, they jump on it. I don't have any concerns.
Positive
Earlier, we used to use our own in-house DNS solutions.
The initial setup is easy to deploy. It is very straightforward.
The Site Reliability Engineering (SRE) team handles the deployment and maintenance tasks. This team is about ten or more people and manages various deployments, not just limited to Cloud DNS.
I do not have specific metrics for cost savings or operational improvements.
Pricing and support are really good. There are no complaints about the pricing.
We primarily use Google Cloud. We found it to be particularly suitable in terms of pricing compared to AWS and others.
I would definitely recommend Google Cloud DNS to other users. We use many Google-related services, and it is pretty easy to manage, reliable, robust, and scalable.
I'd rate the solution eight out of ten.
The product is very user-friendly. We can easily create DNS zones after purchasing the domain. Later, we can assign whatever DNS is required for a specific application. There is support available for any technical issues. It provides a quick reflection feature as well.
Migrating away from Google Cloud DNS can be difficult. At present, we encounter challenges while integrating it with Cloudflare. Additionally, Google could reduce its costs. There are less expensive providers in the market.
We have been using Google Cloud DNS for more than one or two years.
It is a stable product. They provide accessibility and support for the features.
Our development team and front-end customers use the product. We have more than 150 users for Google Cloud DNS.
The initial setup process is easy.
The product is expensive. However, it is worth the cost for the features it provides. In addition, it allows us to purchase the available domain from Google.com. It makes the process of customizing DNS configuration easy.
I recommend Google Cloud DNS an eight out of ten. The software is stable and user-friendly.
I use Google Cloud DNS as a main server. It serves as a public and private domain for our product backlog.
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.
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. If you don’t do them in the exact format, you will get an error message. The product needs to be more clear on UX tips and tricks for adding records. It’s just very basic right now.
I have been using the solution for five years.
The solution is 100 percent stable.
The tool is scalable. I am not aware of the exact numbers but there are more than 1000 users for the product in our company.
The setup is not easy like other Google products like Firebase Hosting which has a super simple step-by-step guide. You just need to type in your domain name after which you will see an IP address and then edit it. In Google Cloud DNS, you have to give a name that matches a specific format.
For example, if you plan to name your zone something like my name like leonard-niehaus.com, it will not work. You need to match the dash format which can be confusing for new users. Cloudflare has email tutorials on doing domains and entering records. You just need to go to the provider. However, on Cloud DNS, you need to more details to see the records, which could be hard to understand.
The initial setup took one hour since we had to configure five systems. I would say if we know about the topic, then the deployment can be completed in about two minutes.
I am not sure about the pricing. However, I can give a rough estimate which is around ten cents per month per zone.
I would rate the solution an eight out of ten. Its stability is super and I am very confident about its reliability. The tool’s pricing is also totally fine. I have removed two points because of the user interface.
The solution is understandable when you are an expert. The product is not hard to learn for newbies. My company uses the product since it is part of Google cloud and we have new products to improve.
I would suggest anyone looking to use the product be very clear about the values that they input to Cloud DNS. I would like to give a walkthrough of the solution to new users since the UX is not clear. I would also get them the format to input the values so they are able to do it.
I would like to add step-by-step setup guides, and general domain authentication features in future releases. I also want to see clearer information about the format for better use in records.
The solution is easy to use. It provides good stability and integration around cloud platforms.
The solution's price could be better.
We have been using the solution for more than ten years.
I rate the solution's stability a ten.
I have configured 20-25 accounts for the solution. I rate its scalability a ten.
The solution's initial setup process is complex as it requires to follow a lot of documentation.
The solution generates a return on investment.
The solution is expensive but cost-effective.
I rate the solution a nine out of ten. I advise others to opt for it if they want a central management system for DNS requirements. But, if they require just one or two DNS configuration options, they should prefer less expensive solutions.
We primarily use the solution in order to manage Google DNS servers. We publish our domain and other software from clients.
The solution is very fast.
It is easy to set up.
The solution is extremely stable.
The scalability is good.
We have been trying recently to route our services via our VMs. However, we can't use that VMs at this point. We had to use internal IDs. It needs to provide better integration.
We'd like to have better documentation.
We've been using the solution for a couple of months.
The solution is extremely stable. There are no bugs or glitches. It doesn't crash or freeze. The reliability is exceptional.
The solution can scale well.
I haven't necessarily dealt with technical support.
The solution is usually pretty simple. However, the way we had to set up items, we had a little bit of trouble.
We are still deploying the solution. It's still a work in progress. We're deployed. However, we are adding more features.
We moved our DNS server from the desktop to GCB, and then we moved everything over to be managed via Google.
The initial setup was handled in-house.
I don't deal with licensing. I can't speak to the exact costs.
We are a reseller.
We are using the latest version of the solution.
I'd recommend the solution to others.
I would advise others not to use anything until they test it. We once tried something without testing it. It cost us a lot of money, and we had to figure out how to remove it. We could have avoided this with pre-testing.
I would rate the solution nine out of ten.
Google DNS is a public service that everybody uses. The tool is probably used by everyone around me, as it is a kind of default DNS service.
The UX of the product is an area with certain shortcomings where improvements are required.
I have experience with Google Cloud DNS. I am a user of the product.
Stability-wise, I rate the solution a ten out of ten.
Scalability-wise, I rate the solution a nine out of ten.
Google Cloud DNS is kind of a default DNS solution. The tool is something that every source relies on, so I cannot cannot give any specific number of people or devices where the product is used, but it is a default DNS.
The solution is used on a daily basis.
My company does not need the support from Google. There is documentation available for help. I rate the support an eight out of ten.
Positive
My company uses the DNS tools from AWS. My company did not switch from the DNS services offered by AWS to Google Cloud DNS. Google Cloud DNS is offered by default, but my company has some services that are completely on the cloud services under AWS. Inside the cloud services offered by AWS, one can use the AWS services. Typically, you don't have a service in one cloud and then rely on a different cloud. Whenever my company wants certain stuff in AWS, we use it.
The product's initial setup phase was moderately easy.
The solution is deployed on a public cloud.
The solution can be deployed in a few minutes.
The solution was deployed with the help of our company's in-house team.
I have implemented Google Cloud DNS in our company's network architecture as it is a standard service available for everybody.
My company has its own type of traffic management solutions that we use with Google Cloud DNS.
The feature of Google Cloud DNS that has been proven to be the most beneficial for your domain management stems from the fact that it is always highly available and is really fast.
Google DNS is always used as a secondary service. If the primary service is not working, it would impact the company, and just one issue would be catastrophic. If Google Cloud DNS is not available, users can use a secondary DNS, and that is automatic failover. Google Cloud DNS is a service that should never fail.
The solution does not require much maintenance from my company's end.
In my company, we have not encountered any scalability issues with Google Cloud DNS as our traffic grew.
I have had a very good experience with the latency and response times of Google Cloud DNS.
I haven't had the need to use the customization capabilities of the product.
I rate the overall tool a nine out of ten.
