You have an Azure resource group named RG1. RG1 contains two virtual networks (VNets) with the following attributes:
* VNet1: East US region; 4 Windows Server virtual machines (VMs)
* VNet2: West US region; 8 Linux VMs
You need to configure host name resolution for all VMs within RG1. Your solution must meet the following technical requirements:
* VMs within each VNet should be able to resolve each other's fully qualified domain names (FQDNs).
* VMs in VNet1 should be able to resolve the host names of VMs in VNet2.
* VMs in VNet2 should be able to resolve the host names of VMs in VNet1.
What should you do?
You should create a private zone in Azure DNS. Within a virtual network, Azure-provided name resolution enables all VMs within a VNet to resolve each other's host names with no additional configuration required. However, Azure-provided name resolution does not work between VNets because VNets are, by design, isolated network communications boundaries.
In this case, you define a private zone in Azure DNS and link both VNets to that zone so the VMs can resolve each other's host names to their corresponding private IP addresses.
You should not define a peering between VNet1 and VNet2. As previously stated, Azure-provided name resolution does not function across VNet boundaries, even with a peering.
You should not deploy a VNet-to-VNet virtual private network (VPN) connection. Although this solution would allow cross-VNet name resolution, it fails to meet the scenario requirement for minimized cost and complexity.