Google Cloud DNS alternatives and competitors

There are two types of DNS. One is DNS which is provided by Azure itself. For example, if you have a testing environment, then you can use that. But if you have a hybrid environment where you link your on-premise with Azure Cloud using a VPN or an express route, then it is better you use the DNS. Not the DNS which is provided by Azure. It is called private DNS. So, you need to use the private DNS so that you can have entries for your on-premise systems as well. We call the named resolution works from on-premise as well. So in a nutshell, there are two DNS which is partly Azure. One is the normal DNS or public DNS service, which is partly Azure. And the second one is the private DNS service which clients can install and they can make use of it.

The most valuable feature is definitely the private one because the public one is generic and you cannot do much modification whereas the private one, allows you to make your own entries.

The technical support can be more knowledgeable.

I have been using the solution for four years.

The solution is very stable. We have not had any stability issues.

The solution is scalable. At the backend, Microsoft will have resiliency built into it. So, you don't have to worry about anything. You just deploy the Software as a Service. Then at the backend, Microsoft will take care of everything.

The technical support is the normal Microsoft tech support. If you have premium support with Microsoft, you can just create a ticket with them and it follows the normal Azure support hierarchy or procedure.

The initial setup is straightforward and not that complex. The software takes probably five to ten minutes to deploy but it is not about deployment, it's about the configuration. You need to configure it according to your environment.

The implementation was completed in-house.

The solution itself is free but you need to pay for the Microsoft Azure infrastructure and host your domains in Azure to use it.

I give the solution a nine out of ten.

I have worked with probably five, or six clients in the last two to three years in consulting. Almost every one of them is using Azure DNS.

I would say make use of Azure DNS. It is a very good solution. Rather than you try to build your own DNS. There are several ways you can build your own DNS. You can put your domain controller in Azure and install DNS on the domain controller because it is domain-integrated, Active Directory-integrated DNS. But that's not required now because there is DNS as a solution. So, you just deploy that service and you're up and running. Instead of putting your own servers in the cloud and trying to replicate your on-premise DNS, just make yourself a built-in DNS service.

Our company uses the solution for DNS services. We purchase domains, create load balancers, set provisions, host websites, and manage how internet traffic routes to websites. The solution handles all DNS queries and translates friendly domain names to numeric IP addresses. 

It is easy to process domain registrations. 

The solution effectively monitors the health of resources and provides good identity access management. 

The solution should include more robust and secure services for hardening sites. Amazon is a public cloud with a very rich set of security features. But, in some cases we find difficulties such as network latencies in terms of hitting particular links. 

I have used the solution across various projects in the past ten years. 

The stability is good but can be affected by a few parameters. The solution hits the load balancer and navigates to the EC2. If any web server, disc, or RAM issues happen, then stability is vulnerable. 

To maintain good stability, it is important to watch inbound and outbound load balancer traffic, check RAM and disc space, and monitor CP utilizations. If you routinely monitor your system with automations and notifications, then you will have no problems with stability. 

Stability is rated a six out of ten. 

The scalability is good so is rated a seven out of ten. 

Technical support is good and can resolve issues both from the customer side and the AWS side. Support is rated a nine out of ten. 

Positive

The setup is easy, takes less than ten minutes, and is rated a nine out of ten. 

The pricing depends on usage and is moderate. 

If you create a domain space in the solution, then you have to use it every time for projects, websites, and documentation. Your cost increases based on usage across months, days, or minutes. 

The solution is good for configuring load balancers and other items. I rate the solution an eight out of ten.