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.

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.

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 are using DNS for our internal active rate repair, not for hosting purposes.

The solution is easy to use and flexible. 

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.

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.