An administrator is configuring name resolution in Azure. The infrastructure includes a Private DNS zone named `corp.local` and two peered virtual networks named `VNet-Hub` and `VNet-Spoke1`. The virtual network `VNet-Hub` is linked to `corp.local` with auto-registration enabled. A virtual machine named `VM-Spoke1` is deployed in `VNet-Spoke1`. Currently, `VM-Spoke1` is unable to resolve names registered within `corp.local`. Which action should the administrator take to allow `VM-Spoke1` to resolve the DNS records?
- AConfigure gateway transit on the virtual network peering between `VNet-Hub` and `VNet-Spoke1`.
- BConfigure the 'Use remote virtual network gateways' setting in the peering properties of `VNet-Spoke1`.
- Add a new virtual network link in `corp.local` that targets `VNet-Spoke1`.Cevap
- DSet the DNS server IP address of `VNet-Spoke1` to point to the IP address of the primary name server for `VNet-Hub`.
Cevap
Add a new virtual network link in `corp.local` that targets `VNet-Spoke1`.
The correct action is to link the spoke virtual network directly to the Private DNS zone. In Azure, DNS resolution for Private DNS zones is scoped strictly to linked virtual networks. Even if a virtual network is peered with another network that is linked to the zone, DNS queries from the peered network will fail unless it also has its own virtual network link.
Adım Adım Çözüm
Anahtar Kavram
Azure Private DNS zones require a dedicated virtual network link for every virtual network from which resolution is needed. Peering two virtual networks does not automatically share or forward Private DNS zone resolution capabilities between them.