Google Cloud DNS Reviews

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.

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.