Azure DNS Reviews

We use the solution for some e-commerce sites that we use. It also integrates with our Kubernetes environment on Azure.

Azure DNS improves our integration with the Kubernetes environment. When we scale or increase our Kubernetes site, the tool updates DNS automatically. It saves us time and cost.

The integration with other services on Azure is valuable. We can create entries automatically by integrating other applications with Azure DNS.

The pricing must be made more clear. If I have multiple domains on Azure DNS, my billing is consolidated. I cannot see the number of connections and requests on each domain. The product must provide information on which DNS or application is consuming the most budget.

I have been using the solution for about two to three years. I am using the latest version of the solution.

I rate the tool’s stability a ten out of ten.

I rate the tool’s scalability a ten out of ten.

I did not need support.

Positive

We also use Amazon Route 53 and Cloudflare. We are consolidating our DNS services into one.

The solution is deployed on the cloud. The initial deployment was a little complex and a little straightforward.

The tool is a good investment.

I use Azure because I had used it previously in another company.

The product did not make any difference in our actual budget. If someone's cloud environment is on Azure, they can choose to use Azure DNS for managing their DNS. If they use Microsoft 365, integrating with Azure DNS will be valuable to them. Overall, I rate the solution a ten out of ten.

If we host a public business solution on Azure, we create a record on DNS to point to the source.

The speed of the queries is valuable. It’s quite fast. It is not a complicated product. We use it alongside other solutions.

The product must be integrated with additional security features.

I have been using the solution for five to six years.

I never had a problem with the tool’s stability. I rate the stability a ten out of ten.

The tool is very scalable. If we need to change our pointers, we just change our records. The administrators use the solution in our organization. I rate the scalability a ten out of ten.

The setup is very straightforward. The setup takes a few minutes. All we need to do is start creating records. It is a cloud solution.

We can do the deployment in-house.

The solution is free.

Overall, I rate the product a nine out of ten.

I use Azure DNS as a local DNS for some servers so that I can connect them using not IP addresses but host names.

The most valuable feature of the solution is that it is a stable product.

There are some issues with the solution's performance where improvements are needed.

I have been using Azure DNS for two years. I use the solution's latest version.

Stability-wise, I rate the solution an eight out of ten. You may face some issues during the installation process of Azure DNS that you can try to fix.

When I deploy Azure DNS in my company, I won't install it on a single node since I always prefer it to be done on multiple nodes.

There are around ten users of Azure DNS in my company since, for us, we use it as a local DNS.

I don't use the solution's technical support. I simply use the guide provided by Microsoft.

I have not used any other solution before Azure DNS in my company.

The initial setup of the product is not complex. I have experience working with servers and operating systems from Windows for over three years, so the setup process of Azure DNS is not Complex for me.

The deployment of Azure DNS can be completed in around an hour and thirty minutes.

The solution is deployed on an on-premises model.

I was involved in the deployment phase of Azure DNS in my company.

To use Azure DNS, I need to buy the license meant for Windows Server.

I rate the overall solution a nine out of ten.

Azure DNS is important when a customer uses a hybrid cloud because we can define exactly the accessibility order, whether it’ll be public or private accessibility. We can use a route for the Azure DNS.

Azure DNS is more secure than other solutions. It's easy to implement since the parameters are easy.

Azure is the only solution in the European Union which accepts GPDA.

I have been using Azure for eight years. 

The product is stable.

I rate the solution’s stability a seven out of ten.

The solution has high scalability. We cater the solution to medium and enterprise.

I rate the solution’s scalability a nine out of ten.

In Belgium, when you want support, there is a communication problem. It should be improved.

Neutral

The initial setup took a few weeks to complete. It includes the implementation followed by testing, and the migration is done after testing.

I rate the initial setup an eight out of ten, where one is difficult and ten is easy.

We have received 8% ROI.

I rate the product’s pricing a seven out of ten, where one is cheap and ten is expensive.

Overall, I rate the solution an eight out of ten.

We have Azure private endpoints and mostly rely on Azure DNS for those private links. We use Azure DNS by default. Some customers like to have their DNS, so we need a DNS portal around Azure, then a traditional portal around a data center.

What I like about Azure DNS is that it doesn't have any issues and integrates quickly with other products. It has good integration, which is incredible.

I also like that whenever you deploy private links and endpoints, Azure DNS gives you the option to select the Azure native DNS, private DNS, or go with the Azure custom DNS. It depends, but if you don't have any dependencies on the DNS, then, like many customers, you won't have DNS issues.

Azure DNS is a very good solution that helps you with domains and other resources.

What needs improvement in Azure DNS is visibility in terms of troubleshooting. It's similar to the area for improvement in Azure Network Watcher, where I can see how the source is going out if I'm troubleshooting a source destination. I can also see the destination. As for seeing how the packet travels, that's what should be improved. It's still lacking in visibility.

Suppose I'm looking into backend machines, and if I'm hitting another NPM machine or any machine on the other side, there should be visibility. The tool should tell you that a specific machine is passing through a VPN gateway or route table, routing to a third-party firewall, and then dropping. Azure DNS should show an accurate answer to help the customers, which is its area for improvement.

I only dealt with Azure DNS a little.

I've never installed Azure DNS because it's there by default.

I have no information on Azure DNS pricing.

My rating for Azure DNS is ten out of ten.

The pricing can be more competitive. 

I have experience with Azure DNS. 

The solution is highly stable. 

We have dependencies also on a local DNS.The scalability is an eight out of ten. 

The initial setup is straightforward. 

The deployment was done in-house. 

The solution is moderately priced. 

Overall, I rate the solution an eight out of ten.

The initial setup is easy and the solution is user-friendly. 

The security features and stability needs to be bettered. 

I have to experience with Azure DNS for two years. 

The stability needs improvement.

It is a scalable solution. Four hundred users are using the solution at the moment. I rate the scalability an eight out of ten. 

The initial setup is straightforward.

I rate the overall solution an eight out of ten. 

It's just the initial setup that we use for managing the internal infrastructure.

The DNS resolution is the most valuable feature.

The solution lacks scalability.

VM-based DNS looks like it's very stable, but the past services is a challenging one.

Scalability is the biggest issue.

The technical support team is good. They are dedicated and try to get to the bottom of the problem.

The initial setup for VMware was a piece of cake for the past services, as I mentioned. But there are a bunch of problems that are related to the way it was configured before past services, and some people from Azure are working hard to find a way to fix it.

The deployment on VMs is intuitive and easy. But for the past services, we had to set up and modify the solution a few times for troubleshooting and looking for a resolution.

I recommend people stick to the VM-based version of Azure DNS. Do not work with past services until some issues get resolved.

I rate the overall solution a six out of ten.