Azure DNS Reviews

Our company manages infrastructures for our customers. 

We use the solution's DNS manager on a daily basis to complete setup and deployment for hosting or configuring applications from IP addresses. There are 5,000 application users within our environment.

No ongoing maintenance is needed unless customers want modifications, enhancements, or changes to networks. 

The solution allows you to host DNS service without using Azure's servers. The DNS is created inside a private zone on Azure which handles all management. 

We do not need as much human effort to manage services because the solution is understandable, easy to use, and includes good automation features.

Queries are handled immediately by the DNS which broadcasts them and sends responses. 

The DNSSEC feature is not yet available on the DNS server so it needs to be added. 

I have been using the solution for four years. 

The solution is stable. 

Technical support is knowledgeable and responds well to us. 

On occasion, there are service delays because technicians are busy on other calls. We understand that some issues require multiple technicians and that needs to be coordinated. We determine if support is moving in the right direction or if we need to close the call and reach out to a different technical team. 

Sometimes we batch tickets into sets of three to get the dealer-level response from support which is very good. 

Support is rated a ten out of ten. 

Positive

I have not used other solutions. 

The setup is easy so I rate it a ten out of ten. 

We implement the solution for our customers. 

The solution is very easy to use or understand and is consumed well. 

I recommend the solution and rate it a ten out of ten. 

We are working at a DSK and use Azure DevOps as we work in Azure DevOps infrastructure engineering. So we use various Azure services. We have migrated Azure services from on-premises to Azure Cloud and multiple services like microservices or application improvements or applications replacing Azure administrators.

The process of creating a virtual mission could be improved.

We have been using this solution for the past four years. It is deployed on-premises. 

It is a stable solution. 

It is a scalable solution. 10 to 15 people are using this solution.

The setup was not difficult.

I rate this solution a seven out of ten because it is a hosting service. However, I would recommend this solution to others.

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.

We use it to connect to our networks from the AD side and resolve host names to IP addresses, identify machines available as per the main domain, and create CNAME records and alias lists in Azure AD.

I've found all of the features to be valuable because we are using it extensively. 

Moreover, Microsoft regularly notifies us about upcoming changes. They have a cycle of introducing features in preview mode before a global release, along with a specific timeline. This helps us stay well-informed.

I would like to see more integration with other platforms, improved stability, enhanced security, and better pricing because there is always room for improvement. 

We've been utilizing Azure DNS for approximately eight years since its inception.

It is a stable solution. 

It's highly scalable and provides very good features from Microsoft. We are satisfied with it.

The support is always good. 

The setup is relatively straightforward. The solution is deployed both on-prem and cloud. 

To deploy it, all you need is a domain name and the necessary preparations. Once you have that, you can begin creating DNS records.

We are using most of the features offered by Azure. We have multiple tools wrapped around it. We have a combination of tools within the organization, and we are content with the setup we have.

I would definitely recommend using the solution. It is a good tool. 

Overall, I would rate the solution an eight out of ten. It provides a wide array of features required from a technical standpoint. It offers a variety of capabilities, and they can confidently adopt it. Most of the essentials are readily available in Azure DNS.

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.

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.

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.