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.
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.
Sr. System & Network Engineer at a manufacturing company with 501-1,000 employees
Real User
Top 20
Jan 25, 2024
We use Azure DNS to host our services. We previously had a different DNS but moved to Azure DNS when we migrated to Azure. We utilize Azure DNS for domain hosting and name resolution in our cloud and hybrid environments.
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.
Cyber Security Specialist at Galeboe Professional Services
Real User
Feb 13, 2023
We use Azure DNS for file storage, office management of our cloud, managing third-party devices, and security protection. Additionally, it integrates well with the other technologies we have.
Security architect at a retailer with 10,001+ employees
Real User
Jan 5, 2023
The DNS (Domain Name System) is a system used to provide domain names for virtual machines on the Azure cloud. Both third-party DNS and Microsoft DNS are options for users of Azure. Microsoft DNS is an inbuilt offering from Microsoft and can be used by those with workloads deployed on Azure. Azure DNS is primarily used for domain name resolution for virtual machines on the cloud.
Sr. Azure DevOps Cloud Engineer at a pharma/biotech company with 10,001+ employees
Real User
Nov 2, 2022
We are working at a DSK and use Azure DevOps as we work in Azure DevOps infrastructure engineering. So we use various Azure services. We have migrated Azure services from on-premises to Azure Cloud and multiple services like microservices or application improvements or applications replacing Azure administrators.
Azure DNS is a hosting service for DNS domains, providing name resolution using Microsoft Azure infrastructure. By hosting your domains in Azure, you can manage your DNS records using the same credentials, APIs, tools, and billing as your other Azure services.
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.
In network-related tasks, I use this DNS to ensure proper end-to-end connectivity.
We use the solution for domains. We manage the name servers using the tool.
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.
We use Azure DNS to host our services. We previously had a different DNS but moved to Azure DNS when we migrated to Azure. We utilize Azure DNS for domain hosting and name resolution in our cloud and hybrid environments.
We use the solution to spare some names and domains from the host to another destination.
If we host a public business solution on Azure, we create a record on DNS to point to the source.
I use Azure DNS as a local DNS for some servers so that I can connect them using not IP addresses but host names.
We use the solution to host IP addresses, sites like microsites.
Azure DNS is used for DNS forwarders and for cloud-native journeys.
It's just the initial setup that we use for managing the internal infrastructure.
We use the solution to manage domains.
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.
We use Azure DNS for file storage, office management of our cloud, managing third-party devices, and security protection. Additionally, it integrates well with the other technologies we have.
The DNS (Domain Name System) is a system used to provide domain names for virtual machines on the Azure cloud. Both third-party DNS and Microsoft DNS are options for users of Azure. Microsoft DNS is an inbuilt offering from Microsoft and can be used by those with workloads deployed on Azure. Azure DNS is primarily used for domain name resolution for virtual machines on the cloud.
We are working at a DSK and use Azure DevOps as we work in Azure DevOps infrastructure engineering. So we use various Azure services. We have migrated Azure services from on-premises to Azure Cloud and multiple services like microservices or application improvements or applications replacing Azure administrators.
Azure DNS is used to reserve name servers. It's typically a service used by the most technical people in our company. It's a mandatory service to use.
Our primary use case is migration from our on-premises environment.