Study guide

8.1 Azure DNS, Private DNS, and Name Resolution

AZ-104 Microsoft Azure Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Orientation and Microsoft Learn Source Control

1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log

2 Chapter 2: Identity, RBAC, and Governance Foundations

2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab

3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization

3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab

4 Chapter 4: Storage Accounts, Access, and Data Protection

4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab

5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep

5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab

6 Chapter 6: Containers, App Service, and Platform Compute

6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab

7 Chapter 7: Virtual Networking, Routing, and Secure Access

7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab

8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting

8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab

9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery

9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab

10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs

10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab

11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path

11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths

8.1 Azure DNS, Private DNS, and Name Resolution

Key Takeaways Explain This Topic AI

Azure DNS hosts public DNS zones, while Azure Private DNS provides name resolution for private VNet-connected resources.

Private DNS zones only resolve from VNets that are linked to the zone, unless hybrid DNS forwarding is configured.

Private endpoints usually require private DNS zone integration so service FQDNs resolve to private IP addresses.

Name resolution troubleshooting starts with the client, resolver path, zone records, VNet links, and caching behavior.

AZ-104 questions often test whether a problem is DNS, routing, NSG filtering, or service firewall configuration.

Last updated: May 2026

Name resolution choices in Azure

Name resolution turns service names into IP addresses, and in Azure it often decides whether traffic uses a public path or a private path. Azure DNS is the managed public authoritative DNS service for zones such as contoso.com . Azure Private DNS is the managed private authoritative service for zones such as privatelink.blob.core.windows.net , corp.internal , or database.contoso.local when those names should resolve inside selected virtual networks.

Azure also provides default name resolution for resources inside a VNet. A VM can usually resolve the names of other VMs in the same VNet without you creating a DNS zone. That default capability is useful, but it is not a full enterprise DNS design. It does not replace a custom DNS server when you need conditional forwarding, on-premises name resolution, cross-environment naming standards, or domain controller integration.

Requirement Best fit Administrator notes

Host public records for an internet domain Azure DNS public zone Delegate the domain at the registrar to Azure name servers.

Resolve private names inside linked VNets Azure Private DNS zone Link each VNet that must resolve records in the zone.

Resolve VM names only inside one VNet Azure-provided DNS Simple, but limited for enterprise hybrid use.

Resolve on-premises and Azure names from both sides Custom DNS plus forwarding Use domain controllers, DNS servers, or Azure DNS Private Resolver patterns.

Resolve private endpoint FQDNs to private IPs Private DNS zone integration The public service name should resolve to the private endpoint address from the private network.

Portal paths are exam-relevant. Use Azure portal > DNS zones for public zones. Use Azure portal > Private DNS zones for private zones. Inside a private zone, use Virtual network links to attach VNets and Recordsets to manage names. For private endpoints, check the DNS configuration blade of the endpoint and the related private DNS zone group.

Public Azure DNS

Azure DNS public zones are authoritative for internet-facing records. You create records such as A, AAAA, CNAME, MX, TXT, and SOA/NS records in the zone. Azure DNS does not buy the domain for you. You still register the domain with a registrar, then delegate the domain to the Azure DNS name servers shown on the zone.

A common web app pattern is to create a CNAME from www.contoso.com to an Azure-provided endpoint, then add the custom domain to the service. For apex domains such as contoso.com , you may need an A record or alias record depending on the target. In AZ-104, avoid assuming DNS alone completes the application mapping. Many services also require the custom domain to be verified or bound at the service.

  • Useful commands: az network dns zone create -g rg-network -n contoso.com
  • az network dns record-set a add-record -g rg-network -z contoso.com -n app -a 20.30.40.50
  • az network dns record-set cname set-record -g rg-network -z contoso.com -n www -c app.contoso.com
  • Azure Private DNS

Azure Private DNS zones answer queries only for networks connected through VNet links or through a DNS forwarding design. A private DNS record can point sql01.corp.internal to 10.20.1.4 , but a VM in another VNet will not resolve it unless that VNet is linked or a resolver forwards queries correctly.

Private DNS zone links have a registration option. Enable auto-registration when Azure should automatically create and maintain records for VMs in the linked VNet. Use it carefully. You can have many resolution links, but registration is a design choice because it controls which VNet can automatically write VM records into the zone. az network private-dns zone create -g rg-network -n corp.internal

  • az network private-dns link vnet create \
  • g rg-network \
  • z corp.internal \
  • n link-spoke1 \
  • v /subscriptions/<sub-id>/resourceGroups/rg-network/providers/Microsoft.Network/virtualNetworks/vnet-spoke1 \
  • e false
  • az network private-dns record-set a add-record -g rg-network -z corp.internal -n app01 -a 10.10.2.15
  • Private endpoints and DNS

Private endpoints are a frequent source of DNS questions. The service FQDN may stay the same, but from the private network it should resolve to the private endpoint IP. For example, a storage account blob endpoint that normally resolves publicly may need to resolve through a privatelink.blob.core.windows.net private DNS zone. If DNS still returns a public IP, traffic may leave the private path and then fail because public network access is disabled or the service firewall blocks the request.

Troubleshooting tree for private endpoint name resolution: Client cannot reach private endpoint service by FQDN

|-- Does nslookup return a private IP from the client subnet?

| |-- No: check private DNS zone, A record, zone group, and VNet link.

| |-- Yes: continue.

|-- Does the route to the private IP stay inside the VNet or peering path?

| |-- No: inspect UDRs, peering, gateway transit, and next hop.

| |-- Yes: continue.

|-- Do NSGs, service firewall rules, or endpoint policies block traffic?

| |-- Yes: correct the blocking rule or service setting.

| |-- No: inspect application port, TLS name, and service health.

Hybrid DNS considerations

Hybrid designs need a resolver path in both directions. Azure VMs may need to resolve on-premises domain names, and on-premises clients may need to resolve Azure private names. A common pattern is to configure VNet DNS servers to point to domain controllers or DNS forwarders, then configure conditional forwarders for Azure private zones. Another pattern uses Azure DNS Private Resolver to provide inbound and outbound endpoints with rulesets.

When VNet DNS server settings are changed, VMs may need a restart or DHCP lease renewal to pick up the new resolver. Linux and Windows clients may also cache results. Always test from the affected client, not only from your workstation.

  • Practical commands: nslookup app01.corp.internal
  • nslookup mystorage.blob.core.windows.net
  • az network vnet show -g rg-network -n vnet-spoke1 --query dhcpOptions.dnsServers
  • ipconfig /displaydns
  • ipconfig /flushdns
  • Exam diagnostics

If a question says an IP address works but the FQDN fails, suspect DNS first. If DNS returns the expected IP but the connection fails, move to NSGs, routes, service firewall, load balancer probes, or the application listener. If one VNet resolves a private name and another does not, check the private DNS VNet links before rebuilding the endpoint.

Do not use public Azure DNS for private-only records that must not resolve publicly. Do not expect a private DNS zone to be globally available without links or forwarding. Do not assume VNet peering automatically links private DNS zones; peering provides network reachability, not DNS zone membership.