An administrator configures an Azure Private DNS zone named corp.adatum.com. The environment contains two virtual networks named VNet-App and VNet-DB that are connected via virtual network peering. The corp.adatum.com zone has a virtual network link to VNet-DB with auto-registration enabled. A virtual machine named VM-DB1 is deployed in VNet-DB and is registered in the zone. A virtual machine named VM-App1 is deployed in VNet-App. From VM-App1, attempts to resolve the name vm-db1.corp.adatum.com fail, although network traffic can flow between the virtual machines. What should the administrator do to resolve the name resolution issue?
- AConfigure the virtual network peering to use gateway transit.
- Link the VNet-App virtual network to the corp.adatum.com Private DNS zone.Answer
- CConfigure the DNS servers setting of VNet-App to point to the IP address of VM-DB1.
- DConfigure a DNS service endpoint on the subnet of VNet-App.
Answer
Link the VNet-App virtual network to the corp.adatum.com Private DNS zone.
To resolve domain names in an Azure Private DNS zone, the virtual network containing the client must have a virtual network link to the DNS zone. Peering alone does not propagate private DNS resolution. Therefore, linking the application virtual network to the private DNS zone is required to allow name resolution.
Step-by-Step Solution
Key Concept
Azure Private DNS Virtual Network Link
Estimated Time:1m 30s