Azure DNS Reviews

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.

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.

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.

We use Azure DNS for file storage, office management of our cloud, managing third-party devices, and security protection. Additionally, it integrates well with the other technologies we have.

Azure DNS provides value beyond its user-friendly interface and easy learning curve.

I have been using Azure DNS for approximately one year.

The scalability could improve.

The stability of the solution is good. It is made with good technology.

We have under 20 people using this solution in my organization.

We have plans to increase our usage. We have people being trained to work.

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

I have not used the support from Azure DNS.

The initial setup of Azure DNS is straightforward. It took us approximately one month to implement.

The solution is worth the money, and we have received a return on investment.

We have five engineers and three managers doing the maintenance.

I would recommend others to go through the training before using the solution.

I rate Azure DNS a 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.

We use private endpoints and we use this solution to ensure that when data is ingested or presented, it doesn't go to any public endpoint where we cant access it.

This solution gives us the ability to stop DODS. We can set up our own V nets and sub nets.

From a security perspective, Microsoft is much better than other cloud providers.

The initial setup of this solution could be less complex and require less manual configurations. 

I have been using this solution for four years. 

This is a stable solution. 

This is a scalable solution.

The initial setup is not that straightforward as this is not a plug and play solution. There are a lot of configurations that need to be completed. From a maintenance perspective, we do not require a big team to handle this. 

We have experienced ROI using this solution. We have been able to define our architecture on Azure Cloud with Data Factory, Synapse and DNS private endpoints. This has saved costs. 

We have an enterprise license agreement with Microsoft. Their pricing is competitive. I would rate it a three and a half out of five. 

I would rate this solution an eight out of ten. 

Our primary use case is migration from our on-premises environment.

The most valuable feature is the ease of installation.

Azure needs to add domain registration to the DNS service.

DNS redundancy services need to be included.

I have been using Azure DNS for seven years.

The stability is good.

Although it is a scalable system, I would rate scalability a three out of five.

We have five DNS administrators.

The technical support team is very good.

The initial setup is straightforward and easy to do.

My advice to others is that this is a quick solution that is easy to install, but it is not a highly scalable one. It works well for smaller companies.

I would rate this solution a seven out of ten.