Examkin

Question

Difficulty: MediumConfigure Azure DNS Private and Public Zones

An administrator deploys an Azure Private DNS zone named `private.contoso.com`. The zone is linked to a virtual network named `VNet1` with auto-registration enabled. The administrator then configures virtual network peering between `VNet1` and a second virtual network named `VNet2`.

Virtual machines in `VNet2` are unable to resolve the DNS records of virtual machines in `VNet1`.

Which action should the administrator perform to resolve this issue?

  1. Add a virtual network link from the private.contoso.com DNS zone to VNet2.Answer
  2. B
    Configure the virtual network peering connection to enable gateway transit.
  3. C
    Configure a user-defined route (UDR) in VNet2 that forwards DNS traffic (destination port 53) to VNet1.
  4. D
    Configure custom DNS servers on VNet2 pointing to the IP address of the Azure-provided DNS service (168.63.129.16) in VNet1.

Answer

Add a virtual network link from the private.contoso.com DNS zone to VNet2.
The correct answer is to add a virtual network link from the private DNS zone to the second virtual network. Azure Private DNS zones require a virtual network link for any virtual network that needs to resolve records within that zone. Although the two virtual networks are peered, name resolution configuration is not shared across peering links automatically.

Step-by-Step Solution

1
Analyze the name resolution requirements for VNet2.
Identify that resources in VNet2 need to resolve records in the private.contoso.com DNS zone.
VNet2 is currently peered with VNet1 but cannot resolve records because virtual network peering does not inherit private DNS zone linkages.
2
Determine the necessary configuration to grant VNet2 access to the private DNS zone.
Recognize that a dedicated virtual network link must be established between the private DNS zone and VNet2.
Azure Private DNS zones require explicit virtual network links for resolution, even if the querying virtual network is peered with a network that is already linked.
3
Select the correct action from the choices.
Adding a virtual network link from the zone to VNet2 is the direct and native way to solve this issue.
This allows Azure's default recursive resolver (168.63.129.16) in VNet2 to query the private DNS zone directly.

Key Concept

Azure Private DNS virtual network links are required for resolution of private DNS zones, and this capability is not transitive over virtual network peering.
Rate this question

Topics

Configure Azure DNS Private and Public Zones

More questions from this topic