Azure DNS seamlessly integrates with Azure services to provide fast and reliable domain name resolution with features like automatic domain record creation and secure integration, optimizing management for enterprises.
| Product | Mindshare (%) |
|---|---|
| Azure DNS | 12.4% |
| Cloudflare | 24.7% |
| Quad9 | 22.8% |
| Other | 40.099999999999994% |
| Company Size | Count |
|---|---|
| Small Business | 8 |
| Midsize Enterprise | 3 |
| Large Enterprise | 17 |
| Company Size | Count |
|---|---|
| Small Business | 210 |
| Midsize Enterprise | 81 |
| Large Enterprise | 271 |
Azure DNS is essential for companies requiring efficient domain name resolution and management of private endpoints. It supports seamless integration with other Azure services, leveraging Microsoft's global network for stability and low-latency DNS resolution. Enterprises benefit from high-availability infrastructure, ensuring connectivity in hybrid environments through reliable domain registration and DNS routing. There is room for growth in addressing latency, visibility, and pricing clarity, with the need for enhanced documentation and security features.
What features make Azure DNS valuable?Azure DNS is pivotal in industries focused on cloud transformation, offering capabilities crucial for migrating services from on-premises to the Azure Cloud. Companies leverage its infrastructure to manage domains, configure network-related tasks like load balancers and traffic managers, and support private DNS connections for both on-premise and Azure environments. Integration with services like Kubernetes aids in managing domains and IP resolutions, highlighting Azure DNS's role in enterprise cloud adoption strategies.
M-Files
| Author info | Rating | Review Summary |
|---|---|---|
| Consultancy Manager at cidns | 4.0 | I’ve used Azure DNS since 2015 and find it scalable, stable with VNet, and easy to set up. While slightly costly, it delivers good ROI through automation. Support quality varies, but overall I rate it 8 out of 10. |
| Works at Northwestern Indiana Telephone Co. | 4.5 | In my network-related tasks, I use Azure DNS for its reliable connectivity and security features. It integrates well with various systems, yielding high ROI due to low charges. It functions effectively as a standard DNS, without needing improvements. |
| Senior Consultant at Hexaware Technologies Limited | 4.5 | In my company, we use Azure DNS for domain registration, but the support from Microsoft in India needs improvement. We experience significant delays, as it takes weeks for technical team responses, causing backlogs in issue resolution. |
| L3 Engineer at Momentum Metropolitan Holdings Limited | 4.0 | I use Azure DNS for managing domains and name servers, and I appreciate its dynamic and secure DNS features, performance, and stability. However, the web interface needs simplification and better integration with DHCP and IP address management platforms. |
| Managing Director at IdeaBytes | 4.0 | We use Azure DNS to route to our application instances and virtual machines, appreciating its straightforward features like A, CAA, and CNAME records. It integrates seamlessly with other Azure services, providing necessary security, though pricing could be improved. |
| Solution Architect at Rackspace Technology | 4.5 | We primarily use Azure DNS for managing domain names and ensuring accurate IP resolution. It integrates well within Azure, offering stable and straightforward configuration through the management console. With proper design, it ensures 100% reliability and uptime performance. |
| Director - Cloud Security at Mastercard | 4.5 | I highly recommend Azure DNS, particularly its stable and scalable private service, for hybrid environments. Setup is straightforward, and it's a valuable solution. My only concern is that technical support could be more knowledgeable. |
| Infrastructure Architect at a security firm with 1,001-5,000 employees | 4.5 | I'm using Azure to host DNS records and appreciate the ease of adding multiple records for the same subdomain. However, domain registration is cumbersome, lacking the flexibility of AWS Route 53, and Azure DNS lacks clear information on certain features. |
| Director of Information Technology at MASFinancials | 3.5 | I use Azure DNS to manage domain names and direct traffic to different destinations. Despite its functionality, there are issues with cloud systems, and currency restrictions in Egypt complicate payments. Setting up an Active Directory requires DNS for domain name translation. |
| Cloud Infrastructure Specialist at Infracommerce | 5.0 | I use Azure DNS for e-commerce sites and its integration with other Azure services is valuable. However, billing clarity is needed to identify domain costs better. While also using Amazon Route 53 and Cloudflare, I find Azure DNS a good investment. |
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.
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 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.
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.
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.
We use the solution for some e-commerce sites that we use. It also integrates with our Kubernetes environment on Azure.
Azure DNS improves our integration with the Kubernetes environment. When we scale or increase our Kubernetes site, the tool updates DNS automatically. It saves us time and cost.
The integration with other services on Azure is valuable. We can create entries automatically by integrating other applications with Azure DNS.
The pricing must be made more clear. If I have multiple domains on Azure DNS, my billing is consolidated. I cannot see the number of connections and requests on each domain. The product must provide information on which DNS or application is consuming the most budget.
I have been using the solution for about two to three years. I am using the latest version of the solution.
I rate the tool’s stability a ten out of ten.
I rate the tool’s scalability a ten out of ten.
I did not need support.
Positive
We also use Amazon Route 53 and Cloudflare. We are consolidating our DNS services into one.
The solution is deployed on the cloud. The initial deployment was a little complex and a little straightforward.
The tool is a good investment.
I use Azure because I had used it previously in another company.
The product did not make any difference in our actual budget. If someone's cloud environment is on Azure, they can choose to use Azure DNS for managing their DNS. If they use Microsoft 365, integrating with Azure DNS will be valuable to them. Overall, I rate the solution a ten out of ten.
