Azure DNS Reviews

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.

We use the solution to manage domains.

It is a robust solution.

They should include more integration with other platforms.

We have been using the solution for one year.

It is a stable solution. I rate its stability as a ten.

Our organization has five solution users and plans to increase usage. It is very scalable.

The solution's technical support team is responsive.

The solution's initial setup process is easy and takes a few minutes to complete. The technical teams for deployment consist of administrators, system engineers, managers, and developers.

We take help from a third-party vendor to implement the solution.

The solution's price is reasonable. We purchase its yearly license.

I rate the solution as a nine.

It's useful in hybrid Microsoft-based services where you need to sync your cloud and on-prem Active Directories or have publc-facing and private interfaces. For example, you're hosting an enterprise application at abc123.com. 

If you're running your enterprise application on Azure, it's convenient to use Azure DNS. It has native integration with other Azure solutions, and Microsoft is a globally recognized DNS provider. You also get CDN services. If you're a media company that requires on-demand data streaming, your DNS plays a vital role by working with CDN services to publish your application. It's cheaper and easier to expand your solution. 

The CDN integration could be improved.

I have used Azure DNS for two or three years. 

Azure DNS requires minimal setup. 

I rate Azure DNS eight out of 10 for affordability. It's cheaper than the native DNS solutions of the other cloud providers in the top three.

I rate Azure DNS seven out of 10. 

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.

We use Azure DNS to host our services. We previously had a different DNS but moved to Azure DNS when we migrated to Azure. We utilize Azure DNS for domain hosting and name resolution in our cloud and hybrid environments.

Azure DNS is a user-friendly and very easy-to-manage solution. The solution's traffic management capabilities, like Azure Front Door, are good.

The solution’s pricing could be improved.

I have been using Azure DNS for more than two years.

I rate Azure DNS an eight out of ten for stability.

A team of ten people uses Azure DNS in our organization on a daily basis.

I rate Azure DNS an eight out of ten for scalability.

The solution’s technical support is good.

Positive

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight or nine out of ten.

The solution was deployed in our organization by an integrator in a few days. Two people are required for the solution’s deployment and maintenance.

Overall, I rate Azure DNS an eight 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.

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. 

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 best feature is the domain register. The other great feature is that whenever you create any resources, Azure DNS will automatically create a record for you.

There are some latency issues that could be improved.

I've been using Azure DNS for almost one year.

If your resources in Azure are in multiple areas of the globe, you need to configure multiple DNS for multiple DNS zones in all regions so that you get higher availability. In case one breaks down, the other one is there for backup.

It is scalable depending on the scenario. We have about 500 users in our company.

We chose Azure DNS because we wanted to use it before we proposed it to our customers. We wanted to be aware of the performance and latencies.

The initial setup of Azure DNS is not too easy nor too difficult. On a scale from one to five with one being hard and five being easy, I would rate the initial setup at 3.5.

If you're ready with all your automation scripts, the deployment should take about 15 minutes.

On a scale from one to ten, I would rate Azure DNS at eight because of the latency issues. Google DNS is a regional-based service, and you get better performance.

Azure DNS is used to reserve name servers. It's typically a service used by the most technical people in our company. It's a mandatory service to use.

The most valuable feature of Azure DNS is it works automatically after configuration. Additionally, the solution is secure.

Azure DNS could improve by having more updates.

I have been using Azure DNS for approximately three months.

Azure DNS is stable.

The scalability of Azure DNS is good, you can add other name servers to it.

Everyone is using this solution in the company. The user does not use it directly, it's a transparent service.

I have not used the support from Azure DNS because the solution works perfectly.

I have not used other solutions prior to Azure DNS.

The initial setup of Azure DNS is easy. We only need to deploy the service in Microsoft Azure, configure it, and that is it. The full deployment can be done in three to four hours.

We did the implementation of the solution in-house. 

The solution payment model is based on how many users use it. This is not an expensive solution, but it can depend on how long we use it. However, if the price was decreased it would be helpful.

We have one system engineer that can do the maintenance of this solution.

I would recommend this solution to others. There is no choice but to use this solution, all companies must use the service because it's a service used by the system.

I rate Azure DNS a nine out of ten.