An organization has a virtual network named `VNet-A` and a peered virtual network named `VNet-B`. To facilitate internal name resolution of resources, a private DNS zone named `corp.internal` has been created. The virtual machines in `VNet-A` require their DNS records to be updated automatically when they are provisioned or deleted. Virtual machines in `VNet-B` must be able to resolve names within `corp.internal`, but their records must not be automatically added to the zone. Which two configuration steps are required to achieve this goal? (Select two.)
- Link the `corp.internal` private DNS zone to `VNet-A` with the auto-registration option enabled.Cevap
- Link the `corp.internal` private DNS zone to `VNet-B` with the auto-registration option disabled.Cevap
- CLink the `corp.internal` private DNS zone only to `VNet-A` and configure virtual network peering transit settings to allow DNS resolution for `VNet-B`.
- DConfigure the custom DNS servers setting on `VNet-B` to point to the IP address of the virtual network link created for `VNet-A`.
Cevap
Link the private DNS zone to the first virtual network with auto-registration enabled, and link the private DNS zone to the second virtual network with auto-registration disabled.
To satisfy the requirements, the private DNS zone must be linked to both virtual networks because name resolution is not transitive across peered networks. Enabling auto-registration on the link to the first virtual network allows automated lifecycle tracking of its VM hostnames. Leaving auto-registration disabled on the link to the second virtual network allows name resolution from that network without registering its VM records in the zone.
Adım Adım Çözüm
Anahtar Kavram
Azure Private DNS Zone virtual network links and auto-registration behavior