Azure DNS and Private DNS Flashcards

Which Azure service provides geo-distributed, authoritative DNS hosting with anycast routing for low latency globally?

Answer: Azure DNS Public Zones

Azure DNS public zones are hosted on Microsoft's global anycast network, providing fast, low-latency DNS resolution from anywhere in the world.

When you create a Private DNS Zone named 'internal.contoso.com' and link it to a VNet, how do VMs resolve names in that zone?

Answer: They use the Azure-provided DNS resolver (168.63.129.16) which queries the linked Private DNS Zone

The Azure internal DNS resolver at 168.63.129.16 automatically queries Private DNS Zones linked to the VNet for name resolution.

What record must exist in an Azure DNS zone for it to be authoritative for the domain?

Answer: SOA (Start of Authority) record

The SOA record defines the authoritative information for the DNS zone and is automatically created by Azure DNS when a zone is provisioned.

Which scenario requires configuring a DNS forwarding ruleset in Azure DNS Private Resolver?

Answer: Resolving on-premises DNS names from Azure workloads using outbound endpoint forwarding rules

A DNS forwarding ruleset attached to the outbound endpoint defines rules that forward Azure-originated DNS queries for specific domains to on-premises resolvers.

What is the impact of setting autoRegistration to true on multiple VNet links to the same Private DNS Zone?

Answer: Each VNet's VMs register in the shared zone, enabling cross-VNet hostname resolution

Multiple VNets can auto-register into the same Private DNS Zone (up to 100), allowing VMs across all linked VNets to resolve each other by hostname.

Which Azure DNS feature allows you to create a record that responds differently based on the client's geographic location?

Answer: Azure DNS does not support geo-routing — use Traffic Manager instead

Azure DNS does not natively support geo-routing; use Azure Traffic Manager or Azure Front Door with DNS for geographic traffic distribution.