An administrator creates an Azure Private DNS zone named private.contoso.com. The administrator configures a virtual network link from private.contoso.com to a virtual network named VNet1 with auto-registration enabled. The administrator then configures a second virtual network link from private.contoso.com to a virtual network named VNet2 with auto-registration disabled. How does this configuration affect the name resolution and registration of the virtual machines deployed in VNet2?
- They can resolve DNS records in private.contoso.com, but their own hostnames are not automatically registered.Cevap
- BThey cannot resolve DNS records in private.contoso.com, and their own hostnames are not automatically registered.
- CThey cannot resolve DNS records in private.contoso.com, but their own hostnames are automatically registered.
- DThey can resolve DNS records in private.contoso.com only if virtual network peering is established between VNet1 and VNet2.
Cevap
Virtual machines in the second virtual network can resolve DNS records in the private DNS zone, but their own hostnames will not be automatically registered.
Linking a virtual network to a Private DNS Zone enables name resolution for virtual machines in that virtual network. Auto-registration is an optional setting that allows Azure DNS to dynamically create and update A records for virtual machines in the linked virtual network. Since the link for the second virtual network does not have auto-registration enabled, its virtual machines can resolve existing records but will not have their hostnames registered automatically.
Adım Adım Çözüm
Anahtar Kavram
Azure Private DNS Zone virtual network links and the role of the auto-registration feature.