Question

Your company runs 40 virtual machines across a single VNet named VNet-Prod. You create an Azure private DNS zone named corp.contoso.com to enable name resolution between the VMs using their host names. After linking the zone to VNet-Prod, you notice that no DNS records for the existing VMs appear in the zone, and new VMs are not being registered automatically. You must ensure that VM host names are automatically registered as A records in corp.contoso.com. What should you do?

Accepted Answer

Recreate the virtual network link to VNet-Prod with auto-registration (registration) enabled.

Answer

Configure a conditional forwarder on each VM pointing to 168.63.129.16.

Answer

Add the private DNS zone as a custom DNS server in the VNet-Prod DNS settings.

Answer

Create a second private DNS zone and enable Azure DNS Private Resolver inbound endpoints.