Azure DNS Reviews

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 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.

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.

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.

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.

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.

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.

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.