Resolution of Azure hostnames from on-premises computers.įorward queries to a customer-managed DNS proxy server in the corresponding virtual network, the proxy server forwards queries to Azure for resolution. See Name resolution using your own DNS server. Resolution of on-premises computer and service names from VMs or role instances in Azure.Īzure DNS Private Resolver or customer-managed DNS servers (on-premises domain controller, local read-only domain controller, or a DNS secondary synced using zone transfers, for example). Name resolution from App Service Web Apps in one virtual network to VMs in a different virtual network. Name resolution from App Service Web Apps to VMs in the same virtual network. Name resolution from an Azure App Service (Web App, Function, or Bot) using virtual network integration to role instances or VMs in the same virtual network.Īzure DNS Private Resolver or customer-managed DNS servers forwarding queries between virtual networks for resolution by Azure (DNS proxy). Name resolution between VMs in different virtual networks or role instances in different cloud services.Īzure DNS private zones, Azure DNS Private Resolver, or Customer-managed DNS servers forwarding queries between virtual networks for resolution by Azure (DNS proxy). Name resolution between VMs located in the same virtual network, or Azure Cloud Services role instances in the same cloud service.Īzure DNS private zones or Azure-provided name resolution If you use Azure Provided DNS then appropriate DNS suffix will be automatically applied to your virtual machines.įor all other options you must either use Fully Qualified Domain Names (FQDN) or manually apply appropriate DNS suffix to your virtual machines. For more information, see Using Azure DNS for private domains. The following table illustrates scenarios and corresponding name resolution solutions:Īzure DNS private zones is the preferred solution and gives you flexibility in managing your DNS zones and records. The type of name resolution you use depends on how your resources need to communicate with each other. Name resolution that uses your own DNS server (which might forward queries to the Azure-provided DNS servers).When resources deployed in virtual networks need to resolve domain names to internal IP addresses, they can use one of four methods: Although you can enable communication by using IP addresses, it's much simpler to use names that can be easily remembered, and don't change. Name resolution for resources in Azure virtual networksĭepending on how you use Azure to host IaaS, PaaS, and hybrid solutions, you might need to allow the virtual machines (VMs), and other resources deployed in a virtual network to communicate with each other.
0 Comments
Leave a Reply. |