Microsoft Certified: Azure Administrator AssociateImplement and manage virtual networkingMedium
A company is migrating its on-premises DNS infrastructure to Azure DNS. They have several public-facing websites and applications that currently use an external registrar. The company wants to host their public DNS zones in Azure DNS to manage them centrally with other Azure resources. What is the first step to host an existing public DNS domain, example.com, in Azure DNS?
- AConfigure NSG rules to allow DNS traffic to Azure DNS.
- BCreate A records for all public-facing resources in the new Azure DNS zone.
- CCreate a new public DNS zone named 'example.com' in Azure DNS.
- DUpdate the NS (Name Server) records at the current domain registrar to point to Azure DNS.
Show answer & explanationAnswer & explanation
Correct answer: C. Create a new public DNS zone named 'example.com' in Azure DNS.
The first step to host an existing public DNS domain in Azure DNS is to create a new public DNS zone in Azure DNS with the same domain name. This action generates the Azure DNS name server records that you will later configure at your domain registrar.
Why the other options are wrong
- A. NSGs are for VNet traffic filtering, not for public DNS resolution. This is irrelevant to hosting a public domain.
- B. Creating A records is an important step, but it must be done *after* the zone is created. The records won't be resolvable until the registrar points to Azure DNS.
- D. Updating the NS records at the registrar is a subsequent step, performed *after* the Azure DNS zone is created and its name servers are known.
Azure Public DNS Zone
A container for DNS records for a specific domain that is publicly resolvable on the internet.
- Hosts DNS records for public domains.
- Managed within Azure portal, PowerShell, CLI, or API.
- Requires updating NS records at the domain registrar.
Memory trick: Create zone, get NS, update registrar, add records.