Azure DNS Reviews

We use the solution to spare some names and domains from the host to another destination.

There are issues with the cloud systems. The Bank of Egypt restricts paying anything through the Internet in dollars. I set up an Active Directory on Azure and joined computers to it. This involved creating a domain controller on Azure and then using DNS to ensure smooth operation over the DC, allowing the controller to translate domain names into IP addresses.

I have been using Azure DNS for ten months.

Ten users are using this solution.

We contact customer support twice a week.

I faced issues with Microsoft, so I migrated my operating system from Microsoft to another platform, such as Linux.

Azure DNS is a compelling choice, where data protection is paramount across cloud platforms. While cloud systems offer significant advantages for small businesses, enterprises may find greater value in comprehensive admin integrations and robust DNS solutions to safeguard their data and operations. In this context, investing in a cloud platform like Azure seems to be the future for small and medium-sized enterprises. On the other hand, on-premises projects or data centers might become obsolete for specific industries due to their limitations in scalability and security compared to cloud solutions.

Overall, I rate the solution a seven 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.

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.

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.

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. 

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.