DEV Community

Cover image for Create DNS zones and configure DNS settings
okunola babatunde
okunola babatunde

Posted on

Create DNS zones and configure DNS settings

Introduction:
Managing communication between workloads becomes much easier when services can connect using domain names instead of complex IP addresses. In this scenario, the organization wants to simplify internal name resolution within its Azure environment without deploying and maintaining a custom DNS infrastructure.

To achieve this, a private DNS zone for contoso.com is created and linked to the application virtual network (app-vnet). This allows resources within the virtual network to automatically resolve internal domain names securely and efficiently. DNS records are also configured for the backend subnet to support seamless communication between workloads and services.

This setup demonstrates how Azure Private DNS can provide a simple, scalable, and cloud-native solution for internal name resolution across Azure virtual networks.

Scenario
Your organization requires workloads to use domain names instead of IP addresses for internal communications. The organization doesn’t want to add a custom DNS solution. You identify these requirements.

  • A private DNS zone is required for contoso.com.
  • The DNS will use a virtual network link to app-vnet.
  • A new DNS record is required for the backend subnet.

Skilling tasks

  • Create and configure a private DNS zone.
  • Create and configure DNS records.
  • Configure DNS settings on a virtual network.

In this lab, I’ve shared a practical and easy-to-follow walkthrough for creating and configuring Azure Private DNS resources. The guide is structured to simplify the deployment process while helping you better understand how private DNS zones, virtual network links, and DNS records work together to support secure and reliable internal communication within Azure environments.

Exercise instructions
Note: This exercise requires the Lab 01 virtual networks and subnets to be installed. A template is provided if you need to deploy those resources.

Create a private DNS zone
Azure Private DNS provides a reliable, secure DNS service to manage and resolve domain names in a virtual network without the need to add a custom DNS solution. By using private DNS zones, you can use your own custom domain names rather than the Azure-provided names.

  1. On the Azure portal, search for and select Private dns zones. Private dns zones
  2. Select + Create and configure the DNS zone. Private dns zones

Property Value
Subscription Select your subscription
Resource group RG1
Name private.contoso.com
Region East US

  1. Select Review + create and then select Create. select Create select Create
  2. Wait for the DNS zone to deploy, and then select Go to resource. Go to resource

Create a virtual network link to your private DNS zone
To resolve DNS records in a private DNS zone, resources must be linked to the private zone. A virtual network link associates the virtual network to the private zone.

  1. In the portal, continue working on the private.contoso.com DNS zone. DNS zone.
  2. In the DNS Management blade, select + Virtual network links. Virtual network links
  3. Select + Add” and configure the virtual network link.

Property Value
Link name app-vnet-link
Virtual network app-vnet
Enable auto registration Enabled
virtual network link

  1. Select Create and wait for the deployment to finish. If necessary, Refresh the page. the deployment to finish the deployment to finish

Create a DNS record set
DNS records provide information about the DNS zone.

  1. In the portal, continue working on the private.contoso.com DNS zone. DNS zone.
  2. In the DNS Management blade, select + Recordsets. Recordsets
  3. Notice that two A records have automatically been created for each of the virtual machines. two A records have automatically been created
  4. Select + Add and configure a record set. When finished select Add. record set

Property Value
Name backend
Type A
TTL 1
IP address 10.1.1.5
a private IP address
Note: This record set implies there is a virtual machine in app-vnet with a private IP address of 10.1.1.5.

Summary:
This exercise focuses on configuring Azure Private DNS to enable internal domain name resolution within an Azure virtual network environment. A private DNS zone is created for contoso.com and linked to app-vnet using a virtual network link, allowing resources in the network to communicate using domain names instead of IP addresses.

Additional DNS records are configured for the backend subnet to support workload connectivity and service discovery. By using Azure’s built-in DNS capabilities, the organization avoids the complexity of deploying and managing custom DNS servers while maintaining reliable and secure internal communication.

Conclusion:
Implementing Azure Private DNS offers a simple and effective way to manage internal name resolution for cloud-based workloads. By linking the private DNS zone to the virtual network and configuring DNS records for backend resources, services can communicate more seamlessly using easy-to-remember domain names instead of complex IP addresses.

This approach not only simplifies network management but also improves scalability and reduces the operational effort required to maintain custom DNS solutions. Overall, Azure Private DNS helps create a more organized, reliable, and user-friendly cloud environment for both administrators and applications.

Key takeaways:

  • Azure Private DNS allows workloads within a virtual network to communicate using domain names instead of IP addresses.

  • Private DNS zones simplify internal name resolution without requiring custom DNS servers.

  • Virtual network links enable DNS zones to be securely associated with Azure virtual networks.

  • DNS records help map domain names to backend resources for easier workload communication and service discovery.

  • Using Azure-native DNS services improves scalability, simplifies administration, and supports secure internal networking.

Top comments (0)