Azure DNS Reviews

Azure DNS is used primarily for hosting and managing public and private DNS zones for customer applications and cloud infrastructure. From a cybersecurity perspective, it provides centralized DNS management, reliable name resolution, and tighter integration with Azure networking, helping to maintain consistent and secure DNS operations across multi-environment deployments.

Another important use case for Azure DNS is supporting hybrid and multi-environment deployments where consistent name resolution is critical. It helps to standardize DNS management across cloud workloads, disaster recovery environments, and private application networks, improving operational consistency and reducing DNS-related issues during migrations and infrastructure changes.

Azure DNS has positively impacted the organization by simplifying DNS administration, improving operational consistency, and reducing the effort required to manage DNS across multiple customer environments. It has also improved service reliability through centralized management, better access control, and faster deployment of DNS changes, helping to support business-critical applications with fewer DNS-related incidents.

Measurable operational benefits have been realized from Azure DNS. DNS-related configuration incidents have reduced by approximately 20 to 25% due to centralized management and access control. DNS change implementation time has decreased by around 50% through automation and infrastructure as code processes. New application and environment deployments have become significantly faster, with DNS provisioning often reduced from hours to a few minutes. Improved governance and standardized DNS management have reduced manual administration effort across multiple customer environments.

The best features of Azure DNS are centralized DNS management, high-availability private DNS zone support, and seamless integration with Azure networking services. From a security and operations perspective, role-based access integration, automation through APIs, and the ability to manage public and private DNS from a unified platform are particularly valuable for enterprise environments.

Automation in Azure DNS allows control, creation, modification, and management of DNS records through infrastructure as code and deployment pipelines, reducing manual effort and configuration errors. Role-based access controls help restrict DNS changes to authorized teams only, improving governance and reducing the risk of accidental or unauthorized modification to critical DNS zones.

Another feature valued in Azure DNS is its reliability and scalability. As a customer environment grows, a large number of DNS zones and records can be managed without additional infrastructure, while benefiting from consistent DNS performance and availability across globally distributed applications.

Azure DNS could be improved with more advanced DNS analytics, richer auditing reporting, and better visibility into DNS query patterns and troubleshooting data. There is also a desire for deeper security-focused features such as enhanced DNS anomaly detection, more detailed change tracking, and stronger integration with broader security monitoring platforms for threat investigations and compliance reporting.

One additional improvement desired in Azure DNS is more advanced DNS security intelligence and automated policy recommendations. For large enterprise environments, features such as DNS anomaly detection, easier cross-zone dependency visibility, and enhanced reporting for compliance and security investigation would provide greater operational and cybersecurity value.

Azure DNS has been in use for two years.

Azure DNS is primarily a DNS hosting and resolution service and does not rely heavily on AI-driven algorithms for its core functionality. The platform's strength is the accuracy and reliability of DNS resolution itself, which has been highly consistent and dependable for enterprise workloads, with few operational issues related to name resolution or record management.

Establishing strong DNS governance, automation, and access control practices from the beginning is recommended for organizations considering Azure DNS. Role-based access control should be used to restrict DNS modification and maintain proper change control. DNS architecture should be planned carefully for hybrid, multi-region, and disaster recovery scenarios to avoid future complexity. The overall review rating for Azure DNS is 8 out of 10.

I have worked with AWS solutions, such as AWS Application Migration Service, Snowball and also provided great feedback about AWS tools, but at the moment, a lot of my customers are based on Azure and it's difficult to use the Amazon tools on Azure.

I work with Azure DNS and I can confirm that. I have worked with Azure DNS from the beginning when I started Azure in 2015.

On my path, I'm considered as an integrator and sometimes a partner of Microsoft.

- Native Integration with Azure Ecosystem: The best feature of Azure DNS is its deep integration with Azure’s global infrastructure, providing high‑availability, low‑latency DNS resolution without you having to manage DNS servers.

- Global High‑Availability Infrastructure: Azure DNS runs on Microsoft’s global network of name servers, offering:

• 99.99% uptime SLA.

• Redundant and distributed DNS resolution.

• Low latency lookups worldwide without extra configuration.

  
  

- Private DNS Zones: Supports internal name resolution inside one or more VNets, without running your own DNS servers.

• Add native management routing (geo‑routing, failover, weighted records) directly within Azure DNS zones to reduce dependency on extra services.


• Cost Efficiency: Offer bundle pricing tiers or discounts for high‑volume enterprise customers, or an option for cost‑optimized internal DNS zones. 


• Improved Error Diagnostics: Provide more descriptive error codes and guided troubleshooting steps in the portal or CLI.

I worked with Amazon Neptune until 2022, 2021, 2022, and 2023.

A stable solution depends on whether you use VNet or another option; VNet allows for the stability that we want.

The rating for technical support from Azure DNS depends on what your amount cost is. Sometimes you make a standard support which is 24. You have three hours of before support, and business support is different; you have 24/7 support based on what you pay.

Positive

The initial setup of Azure DNS is not complex; I have seen more complex solutions than that. For me, it's easy and friendly.

- Direct reduction in operational overhead and infrastructure spend, 

- Faster deployments mean quicker application rollouts and feature delivery, 

- High Availability Reduces Downtime Costs, 

- Avoids capital expenditures for over‑provisioning. 

ROI for Azure DNS is high, especially for enterprises running workloads at scale. The automation, high availability, and operational simplicity translate directly into time and cost savings.

I have already worked with Amazon Neptune, with their tool.

I can answer questions about this solution if it's in my competence.

For the past 12 months, I haven't worked with this solution because a lot of my customers are based on Azure, making it difficult to use the Amazon tools on Azure.

My company name is C I D N S. It is my own company.

My title is Consultancy Manager.

My email address is dieudonne.nsabimana@cidns.eu.

I rate Azure DNS an 8 out of 10.

In network-related tasks, I use this DNS to ensure proper end-to-end connectivity.

Azure DNS provides end-to-end P2P connectivity and enhances security, making it more secure and reliable. This is critical in ensuring proper network communication and security. Its integration capabilities are also noteworthy, as it seamlessly integrates with different systems, ensuring smooth connectivity across platforms.

I did not see any improvements required. It functions as a standard DNS, which is very important, and it does not need separate improvements.

I have experience using Azure DNS for around seven plus years.

I rate the stability as nine out of ten.

I can say probably nine or ten out of ten, as even with minimal knowledge, it can be set up quickly, and there are different setups like the traffic manager.

Technical support is minimally required for DNS-related tasks if you have previous experience. However, if needed, I would rate Azure's technical support as seven out of ten.

Neutral

Previously, on-premises, I worked with different DNS setups.

DNS is always straightforward. There are no specific skills required to set it up as it follows common IP-based configurations.

The ROI is always high because Azure DNS setup is essential and does not incur high charges. They charge based on the number of enabled zones, and some queries are offered for free monthly. DNS is mandatory.

Pricing is not very high. Azure DNS charges based on the number of zones enabled, offering some free queries monthly, which keeps costs low.

I would recommend Azure DNS to others and rate the solution overall as nine out of ten.

In my company, the solution is used for our domain registration.

The support from Microsoft in India is an area of concern where improvements are required. My company has to wait for a couple of weeks after raising a ticket with Microsoft's technical team to get our issues resolved, which leads to a lot of backlogs.

I have been using Azure DNS for three to four years. I am a customer of the product.

It is a very stable solution. My company hasn't faced any stability issues.

Microsoft outsources the services related to its support team, which is not a good thing.

I rate the technical support a six to seven out of ten.

Neutral

I would describe Azure DNS as a cheaply priced product.

Azure DNS has improved our company's domain management and resolution reliability since it provides most of the solutions, especially whatever is required in our organization.

My experience of integrating Azure DNS into our company's existing cloud services was easy.

For the security and privacy aspect, my company mostly relies on Microsoft. I don't have the expertise to comment on whether Azure DNS has influenced our company's operations from a security and privacy perspective.

Azure DNS is a really good product when it comes to scalability and performance for our company's workload.

Azure DNS has helped my company with the disaster recovery phase. The product uses cloud features, and since my company has separate regions, we have a backup tool or a backup deduplication technology.

The implementation of Azure DNS in our environment benefits the entire organization, but four to five people have access to the solution.

I rate the overall product a nine to ten out of ten.

We use the solution for domains. We manage the name servers using the tool.

The solution has improved our web application’s accessibility and speed. The tool makes it easier to configure and manage.

I like Dynamic DNS and secure DNS features. The tool is easy to manage and use. I like its performance and stability. It is a secure product.

The web interface to manage the solution must be made easier. The tool must provide seamless integration between DHCP and IP address management platforms.

I have been using the solution for 15 years.

I rate the tool’s stability seven and a half out of ten. The stability must be improved.

The tool is scalable. We have more than 2000 servers and more than 20,000 desktops.

The support is quite helpful.

The initial setup was very simple. The time taken for deployment depends on the environment’s requirements. The setup depends on the environment. The setup becomes complex when the environment is big.

The pricing depends on our agreement with Microsoft.

I will recommend the product to others. It is easy to use and manage. Overall, I rate the solution an eight out of ten.

We use Azure instances for our applications. When somebody types the application names, we use the DNS to route to the instance or virtual machine. We use the tool for DNS routing.

DNS gives a very fast response to the IP address. The response is fast because the virtual machines are also in Azure. When I type the application URL and reach Azure’s domain manager, it provides the virtual machine’s IP address. I can access the IP address. I don't need to remember it.

Azure DNS is a straightforward application. We just have to create the entries. We can enter every domain and subdomain that can be a threat to us. The product has all the features. It has many records, such as A and CAA records. There is something called a CNAME record. When we type it, it gives the corresponding IP address. There are several ways to define the domains and subdomains.

The integration with other Azure services is good. The solution is part of the ecosystem, so it helps to integrate with other Azure services easily. The integration is seamless. The tool has security features. People cannot change things without proper authorization. The product has a domain-locking feature. It stops people from misusing the tool. The solution serves all our requirements.

The solution must provide better pricing.

I have been using the solution for 1 year.

I rate the stability 10 out of 10. The tool is highly stable.

The product is highly scalable. I rate the scalability 8 out of 10. The scalability is helpful in general. We are a small company.

The support is part of Microsoft. We get good support.

Neutral

I rate the ease of setup a 9 out of 10. The initial setup is very easy. The solution is deployed on the cloud. The deployment takes a few hours.

The solution is not cheap, but it is not expensive. I rate the pricing a 5 or 6 out of 10.

We are ISV partners. I will definitely recommend the product to others. It is easy to set up. It is scalable. Microsoft provides reliable services. It is easy to integrate the solution with other tools in the Azure ecosystem. Overall, I rate the solution 8 or 9 out of 10.

It's primarily used for managing domain names and ensuring proper resolution of IPs and domains. This is essential for setting up load balancers, traffic managers, and other network-related configurations.

Azure DNS is mainly focused on providing name resolution services. Its primary function is to ensure that domain names are correctly resolved to the corresponding IP addresses. As for the integration with other Azure services, it's tightly integrated like any other service within the Azure ecosystem.

There's always room for improvement in any product. 

The reason I rate it highly is because within Azure, everything is managed through a single console called the Microsoft Azure management console. This console provides access to all the features and configurations, including DNS. You can easily browse through the menus, enable or disable features as needed, without having to deal with complex configurations. Additionally, Azure DNS is constantly stable, and each option in the console provides clear information about its impact when enabled or disabled. This makes it straightforward and simple for anyone to configure.

I have been using Azure DNS for the past 5 years.

As for scalability, Azure DNS is indeed scalable, but there are limitations due to its nature as a specialized service. Currently, around two thousand users are utilizing DNS, and yes, there are plans to expand its usage further

Azure DNS needs to be consistently stable because any failure can make our organization unreachable from outside. It's crucial for DNS to be stable 24/7, as even a momentary failure can disrupt accessibility. In terms of stability, I would rate it a solid eight out of ten. While it's stable, there's always room for improvement to ensure it remains reliable.

We've had interactions with Microsoft, although not specifically related to DNS. Generally, we've discussed various matters with them. If any issues arise at the DNS level, we would likely reach out to Microsoft for assistance, as they are the service provider. However, personally, I haven't contacted Microsoft for DNS-related issues. 

Azure DNS is designed to support a hundred percent reliability. If implemented correctly with the right design, it can ensure uninterrupted uptime, performance, and reliability. However, the actual reliability may vary depending on how it's built and deployed in different organizations. In our organization, we've implemented it to achieve a hundred percent reliability, but it's uncertain how others may configure it.

In my opinion, DNS is inexpensive. The pricing depends on how you use it, but overall, it's quite affordable. It typically costs just a fesw cents, and Microsoft even offers ten thousand free hits per month.

Overall, I'd recommend Azure DNS for anyone starting out, as it's an essential service used by everyone on a daily basis. I would rate Azure DNS a solid ten. It's crucial for DNS to be consistently online, as even a brief downtime can disrupt access to websites. Building DNS with the right level of redundancy and high availability ensures uninterrupted service. However, the reliability ultimately depends on how the product is built and the specific requirements of the developers. I would rate it high as well, maybe not a perfect ten, but at least a nine.

There are two types of DNS. One is DNS which is provided by Azure itself. For example, if you have a testing environment, then you can use that. But if you have a hybrid environment where you link your on-premise with Azure Cloud using a VPN or an express route, then it is better you use the DNS. Not the DNS which is provided by Azure. It is called private DNS. So, you need to use the private DNS so that you can have entries for your on-premise systems as well. We call the named resolution works from on-premise as well. So in a nutshell, there are two DNS which is partly Azure. One is the normal DNS or public DNS service, which is partly Azure. And the second one is the private DNS service which clients can install and they can make use of it.

The most valuable feature is definitely the private one because the public one is generic and you cannot do much modification whereas the private one, allows you to make your own entries.

The technical support can be more knowledgeable.

I have been using the solution for four years.

The solution is very stable. We have not had any stability issues.

The solution is scalable. At the backend, Microsoft will have resiliency built into it. So, you don't have to worry about anything. You just deploy the Software as a Service. Then at the backend, Microsoft will take care of everything.

The technical support is the normal Microsoft tech support. If you have premium support with Microsoft, you can just create a ticket with them and it follows the normal Azure support hierarchy or procedure.

The initial setup is straightforward and not that complex. The software takes probably five to ten minutes to deploy but it is not about deployment, it's about the configuration. You need to configure it according to your environment.

The implementation was completed in-house.

The solution itself is free but you need to pay for the Microsoft Azure infrastructure and host your domains in Azure to use it.

I give the solution a nine out of ten.

I have worked with probably five, or six clients in the last two to three years in consulting. Almost every one of them is using Azure DNS.

I would say make use of Azure DNS. It is a very good solution. Rather than you try to build your own DNS. There are several ways you can build your own DNS. You can put your domain controller in Azure and install DNS on the domain controller because it is domain-integrated, Active Directory-integrated DNS. But that's not required now because there is DNS as a solution. So, you just deploy that service and you're up and running. Instead of putting your own servers in the cloud and trying to replicate your on-premise DNS, just make yourself a built-in DNS service.

Azure DNS is used for DNS forwarders and for cloud-native journeys.

The most valuable features of Azure DNS are the DNS forwarder and the DNS additional record editions.

Azure DNS sticks mostly with the Azure native solution and doesn't scale well in a multi-cloud or hybrid environment. A lot of functionalities are not available in the hybrid cloud.

A public DNS resolver should be included in the next release.

I have been working with Azure DNS for almost two years.

Azure DNS is a very stable solution, and I rate Azure DNS a ten out of ten for stability.

I rate Azure DNS a seven out of ten for scalability. Azure DNS's scalability is good and can scale even better for large enterprises. Our clients are mostly enterprise businesses.

Microsoft’s technical support for Azure DNS is very good.

Positive

Azure DNS's initial setup is very easy.

Just one engineer is required to deploy the solution within a few hours. Just one person is required for the solution's maintenance.

Azure DNS is a cheap solution, and I rate it a two out of ten for pricing. Azure DNS has a monthly licensing fee, and there are no additional costs besides the licensing cost.

We use the latest version of Azure DNS. Use Azure DNS if your primary journey is in Microsoft Azure. If you want to move to a hybrid or on-prem solution with Azure or AWS, try avoiding Azure DNS.

Overall, I rate Azure DNS an eight out of ten.

I am using Azure to host the DNS records.

I like the feature where I can add multiple DNS records for the same subdomain.

Domain registration is one of the problems. We need to go to application services or web apps to purchase the domain instead. If that were to be equivalent to AWS's Route 53 that would be good. But, it is not as flexible as that.

Also, there is no clear information on the functionality of Azure DNS or the features of Azure DNS. For example, there is no information provided on the DDI feature and whether it is available or not.

I have been using this solution for more than two years.

It is stable. We did not have an issue.

It is an easily scalable solution. I would the scalability a nine out of ten.

The support team is good. They support well and we don’t have to implement anything. Since we have a premium plan, the response time is probably less than one hour.

The initial setup is straightforward.

I deployed the hybrid version because the domains are posted somewhere, and I am using DNS on Azure.

I did the installation by myself as it is easy. 

The price is low and it's a reasonable price for that product.

I recommend the product to the users.