Question

Your company runs several virtual machines in a VNet named VNet-Prod. You create an Azure private DNS zone named contoso.internal to allow the VMs to resolve each other by hostname. After creating the zone, you notice that no DNS records for the existing VMs appear in the zone, and the VMs cannot resolve each other's names. What must you do to enable automatic creation of DNS records for VMs in VNet-Prod?

Accepted Answer

Create a virtual network link between the private DNS zone and VNet-Prod with auto-registration enabled.

Answer

Add a public IP address to each VM so the DNS records can be created.

Answer

Configure a conditional forwarder in Azure DNS pointing to VNet-Prod.

Answer

Create A records manually for each VM in the contoso.internal zone; auto-registration is not supported for private zones.