www.kodekloud.com into a browser, a DNS resolution process begins. The user’s device typically queries a recursive resolver (for example, an ISP resolver), which then asks the authoritative name servers for the domain. If Azure DNS hosts your zone, Azure’s authoritative name servers receive the query and return the IP address—allowing the browser to connect to the service.
The diagram below visualizes this end-to-end process, showing multiple Azure name servers for redundancy and high availability. In this example, one name server responds with the correct IPv4 address 172.67.68.105, enabling access to the Azure-hosted service.

Example: Create a public A record using Azure CLI
- Low latency: Azure DNS is globally distributed, serving queries from locations close to the requester to reduce response times.
- High availability: Each DNS zone gets multiple authoritative name servers to maintain resolution availability even if some servers are unreachable.
- Fully managed: Microsoft operates the DNS infrastructure, removing the need to deploy or maintain public DNS servers.
- Reliability and resiliency: Public DNS zones in Azure benefit from Microsoft’s global network, redundancy, and operational practices.

Azure DNS provides authoritative DNS hosting but does not register domain names. Register your domain with a domain registrar, then configure the registrar’s name server settings to use the Azure DNS name servers for your zone.
- Learn how to create and manage public DNS zones and records in the Azure portal: Azure DNS documentation.
- For automation, see the Azure CLI and ARM template guides: Create DNS records with Azure CLI and Deploy DNS with ARM templates.
- For advanced scenarios (traffic management, alias records, and private DNS integration), review the Azure DNS features and best practices in the Azure networking documentation.