The session introduces Azure DNS as a way to map readable names, such as learn.microsoft.com, to backend IP addresses.
Azure DNS management includes DNS for Microsoft Entra ID, public DNS zones for internet-resolvable resources, and private DNS zones for internal Azure resources.
Custom Domains in Entra ID
A Microsoft Entra tenant receives a default domain ending in onmicrosoft.com, such as contoso.onmicrosoft.com.
To use a custom domain such as contoso.com, you must purchase it from a registrar or supported Azure-related services, then add it under Custom domain names in Entra ID.
Before Entra ID can verify a custom domain, you must create either the provided TXT record or MX record in the registrar's DNS settings.
After the registrar record is added and verification succeeds, the custom domain can be made primary and used for new or existing user accounts.
Public DNS Zones
DNS zones can be used to resolve internet-facing Azure resources by name instead of public IP address, such as webserver.contoso.com.
Creating a DNS zone requires an existing purchased domain name, then Azure provides name server records for that zone.
All four Azure-provided NS records must be copied to the domain registrar so internet DNS queries can be delegated to Azure DNS.
Record sets define resource mappings; an A record maps an IPv4 hostname such as webserver.contoso.net to an IP address.
NSLookup can be used to test that a DNS name resolves to the expected IP address once the DNS records and delegation are configured.
Private DNS Zones
Private DNS zones resolve names only inside linked Azure virtual networks and are not resolved over the internet.
Private DNS zones do not require purchasing a public domain or configuring registrar records.
A virtual network must be linked to a private DNS zone before resources in that network can use the private DNS records.
Manual private DNS records can be created, such as appserver.fabricam.net resolving to a private IP address like 10.7.0.4.
Auto-registration can automatically create DNS records for virtual machines in a linked virtual network using the VM names.
Auto-registration supports up to 100 virtual networks per private DNS zone, though more virtual networks can be linked without auto-registration.
Because auto-registration uses VM names, clear virtual machine naming conventions help produce useful DNS names.
Session Wrap-Up
The module covered managing Azure virtual networks, network security groups, and Azure DNS.
The presenter recommends reviewing Microsoft Learn reference modules and knowledge checks to reinforce the material.
Actiepunten
Review the reference modules and check your knowledge questions on Microsoft Learn at aka.ms/learn.
