Examkin

Question

Difficulty: MediumConfigure Azure DNS Private and Public Zones

You manage an Azure subscription that contains a private DNS zone named corp.internal.

You have two virtual networks named VNet-Prod and VNet-Dev that are connected via virtual network peering.

The corp.internal private DNS zone is linked to VNet-Prod with auto-registration enabled. Several virtual machines in VNet-Prod have automatically registered their DNS records in the zone.

You deploy a new virtual machine named VM-Dev1 in VNet-Dev.

You discover that VM-Dev1 cannot resolve the DNS names of the virtual machines in VNet-Prod using the corp.internal suffix.

You need to ensure that VM-Dev1 can resolve the DNS names in corp.internal.

What should you do?

  1. Create a virtual network link from the corp.internal private DNS zone to VNet-Dev.Answer
  2. B
    Enable gateway transit on the virtual network peering between VNet-Prod and VNet-Dev.
  3. C
    Enable auto-registration on the virtual network peering connection from VNet-Prod to VNet-Dev.
  4. D
    Configure the DNS server settings of VNet-Dev to point to the private IP address of the virtual network gateway in VNet-Prod.

Answer

Create a virtual network link from the corp.internal private DNS zone to VNet-Dev.
Creating a virtual network link from the corp.internal private DNS zone to VNet-Dev is required because Azure Private DNS zones require an explicit link to any virtual network that needs to resolve its DNS records. Peering two virtual networks enables IP routing between them but does not automatically extend Private DNS zone resolution capabilities to the peered network.

Step-by-Step Solution

1
Identify the requirement: A virtual machine in VNet-Dev needs to resolve DNS records in the corp.internal Private DNS zone.
Determine that name resolution requires a virtual network link between VNet-Dev and corp.internal.
By default, Azure Private DNS zones are only resolvable by virtual networks that have an active virtual network link associated with the zone. Peering alone does not propagate Private DNS zone resolution.
2
Configure the virtual network link in the Azure Portal, CLI, or PowerShell.
Create a new virtual network link for the private DNS zone corp.internal pointing to VNet-Dev.
Linking VNet-Dev to the private DNS zone allows resources in VNet-Dev (such as VM-Dev1) to query the Azure default DNS IP (168.63.129.16) and resolve names within that zone.

Key Concept

Azure Private DNS Zone Virtual Network Links
Rate this question

Topics

Configure Azure DNS Private and Public Zones

More questions from this topic