Examkin

Soru

Zorluk: OrtaConfigure Azure DNS Private and Public Zones

Your company implements a split-horizon DNS configuration in Azure. You have a public Azure DNS zone named `adventure-works.com` and an Azure Private DNS zone also named `adventure-works.com`. The Private DNS zone is linked to a virtual network named `VNet-App`.

The public DNS zone contains a CNAME record named `portal` that points to an external SaaS application.

Users on virtual machines in `VNet-App` report that they cannot resolve the name `portal.adventure-works.com`.

Which of the following actions should you perform to resolve the name resolution issue for the virtual machines in `VNet-App`?

  1. A
    Configure a user-defined route (UDR) in VNet-App that forwards DNS traffic to the public IP address of the Azure DNS service.
  2. B
    Enable auto-registration on the virtual network link between VNet-App and the Private DNS zone.
  3. Create a CNAME record named portal in the Private DNS zone adventure-works.com that points to the external SaaS application.Cevap
  4. D
    Create a DNS delegation record in the public DNS zone adventure-works.com that points to the Azure Private DNS name servers.

Cevap

Create a CNAME record named portal in the Private DNS zone adventure-works.com that points to the external SaaS application.
When a virtual network is linked to an Azure Private DNS zone, all name resolution requests for that namespace from within the virtual network are handled by the Private DNS zone. If a requested record does not exist in the Private DNS zone, Azure DNS does not query the public DNS zone of the same name. Therefore, to resolve the record from the virtual network, a corresponding record must be manually created in the Private DNS zone.

Adım Adım Çözüm

1
Analyze how DNS resolution works in a split-horizon layout with Azure Private DNS.
When a virtual network is linked to an Azure Private DNS zone, all DNS queries originating from that virtual network for that namespace (e.g., adventure-works.com) are resolved exclusively by the Private DNS zone.
Azure DNS does not fall back to the public DNS zone for queries that fail to resolve in the private zone with the same name.
2
Identify where the missing DNS record needs to be created.
The CNAME record for portal must be created within the Private DNS zone adventure-works.com.
Because the private zone is the authoritative source for name resolution within VNet-App, adding the record to the private zone allows the internal VMs to resolve it.

Anahtar Kavram

In a split-horizon DNS setup, an Azure Private DNS zone is authoritative for its namespace within any linked virtual networks. Azure DNS does not query the public DNS zone of the same name if a record is not found in the private zone. Therefore, any record in the public zone that needs to be resolved from a linked virtual network must also be created in the private DNS zone.
Bu soruyu puanla

Konular

Configure Azure DNS Private and Public Zones

Bu konudan daha fazla soru