To support a new internal application architecture, you deploy a virtual network named `VNet-Core` and create two Azure Private DNS zones named `corp.internal` and `services.internal`.
You attempt to create virtual network links from `VNet-Core` to both private DNS zones, enabling the auto-registration setting on both links.
What is the outcome of this configuration?
- The second virtual network link will fail to be created because a virtual network can be linked to only one private DNS zone with auto-registration enabled.Answer
- BBoth links will be created successfully, and the virtual machines in `VNet-Core` will automatically register their DNS records in both private DNS zones.
- CBoth links will be created successfully, but the virtual machines in `VNet-Core` will only automatically register their DNS records in the private DNS zone that was linked first.
- DThe configuration will fail because a virtual network can only be linked to a single private DNS zone, regardless of whether auto-registration is enabled.
Answer
The second virtual network link will fail to be created because a virtual network can be linked to only one private DNS zone with auto-registration enabled.
Azure Private DNS allows a virtual network to be linked to multiple private DNS zones for name resolution. However, a virtual network can only be linked to a single private DNS zone with auto-registration enabled. Attempting to enable auto-registration on a second link for the same virtual network will fail during deployment.
Step-by-Step Solution
Key Concept
Virtual network link limitations in Azure Private DNS