Mod 4 - Lab - Configure Azure DNS
Mod 4 - Lab - Configure Azure DNS
Mod 4 - Lab - Configure Azure DNS
Scenario
Lab: Configure Azure DNS
All tasks in this lab are performed from the Azure portal (including a PowerShell Cloud Shell session)
Objectives
Exercise 1:
❕ Note: When not using Cloud Shell, the lab virtual machine must have the Azure PowerShell 1.2.0 module (or newer) installed
Configure Azure
DNS for public https://docs.microsoft.com/en-us/powershell/azure/install-az-ps
domains
Labfiles\Module_04\Configure_Azure_DNS\az-100-04_azuredeploy.parameters.json
Scenario
Adatum Corporation wants to implement public and private DNS service in Azure without having to deploy its
own DNS servers.
Objectives
1. From the lab virtual machine, start Microsoft Edge, browse to the Azure portal at http://portal.azure.com
and sign in by using a Microsoft account that has the Owner role in the Azure subscription you intend to
use in this lab.
3. From the New blade, search Azure Marketplace for DNS zone.
5. From the Create DNS zone blade, create a new DNS zone with the following settings:
Subscription: the name of the Azure subscription you are using in this lab
Name: any unique, valid DNS domain name in the .com namespace
Resource group location: (US) East US (or a supported region near you)
1. From your lab computer open a Powershell session, run the following in order to identify the public IP
address of your lab computer:
Code Copy
❕ Note: Take a note of this IP address. You will use it later in this task.
2. From the Azure Portal, start a PowerShell session in the Cloud Shell.
❕ Note: If this is the first time you are launching the Cloud Shell in the current Azure subscription, you will be asked to
create an Azure file share to persist Cloud Shell files. If so, accept the defaults, which will result in creation of a storage
account in an automatically generated resource group.
3. In the Cloud Shell pane, run the following in order to create a public IP address resource:
Code Copy
5. From the az1000401b-RG resource group blade, navigate to the blade displaying newly created public
DNS zone.
6. From the DNS zone blade, click + Record set to navigate to the Add record set blade
Name: mylabvmpip
Type: A
TTL: 1
IP ADDRESS: the public IP address of your lab computer you identified earlier in this task
8. From the Overview blade, click + Record set, and create another record with the following settings:
Name: myazurepip
Type: A
Choose a subscription: the name of the Azure subscription you are using in this lab
TTL: 1
Task 3: Validate Azure DNS-based name resolution for the public domain
1. On the DNS zone blade, note the list of the name servers that host the zone you created. You will use the
first of them named in the next step.
2. From the lab virtual machine, start Command Prompt and run the following to validate the name resolution
of the two newly created DNS records (where <custom_DNS_domain> represents the custom DNS
domain you created in the first task of this exercise and <name_server> represents the name of the DNS
name server you identified in the previous step):
Code Copy
3. Verify that the IP addresses returned match those you identified earlier in this task.
❕ Result: After you completed this exercise, you have created a public DNS zone, created a DNS record in the public DNS zone,
and validated Azure DNS-based name resolution for the public domain.
4. Validate Azure DNS-based name reservation and resolution for the private domain
1. From the Azure Portal, start a PowerShell session in the Cloud Shell.
2. In the Cloud Shell pane, run the following in order to create a resource group:
Code Copy
3. In the Cloud Shell pane, run the following in order to create two Azure virtual networks:
Code Copy
1. In the Cloud Shell pane, run the following in order to create a private DNS zone with the first virtual
network supporting registration and the second virtual network supporting resolution:
Code Copy
2. In the Cloud Shell pane, run the following in order to verify that the private DNS zone was successfully
created:
Code Copy
2. In the Cloud Shell pane, run the following in order to deploy an Azure VM into the first virtual network:
Code Copy
cd $home
3. In the Cloud Shell pane, run the following in order to deploy an Azure VM into the second virtual network:
Code Copy
❕ Note: Wait for both deployments to complete before you proceed to the next task. You can identify the state of the jobs by
running the Get-Job cmdlet in the Cloud Shell pane.
Task 4: Validate Azure DNS-based name reservation and resolution for the private domain
1. In the Azure portal, navigate to the blade of the az1000402b-vm2 Azure VM.
2. From the Overview pane of the az1000402b-vm2 blade, generate an RDP file and use it to connect to
az1000402b-vm2.
Password: Pa55w.rd1234
4. Within the Remote Desktop session to az1000402b-vm2, start a Command Prompt window and run the
following:
Code Copy
nslookup az1000402b-vm1.adatum.corp
6. Switch back to the lab virtual machine and, in the Cloud Shell pane of the Azure portal window, run the
following in order to create an additional DNS record in the private DNS zone:
Code Copy
7. Switch again to the Remote Desktop session to az1000402b-vm2 and run the following from the
Command Prompt window:
Code Copy
nslookup www.adatum.corp
❕ Result: After completing this exercise, you have provisioned a multi-virtual network environment, created a private DNS zone,
deployed Azure VMs into virtual networks, and validated Azure DNS-based name reservation and resolution for the private
domain
1. At the top of the portal, click the Cloud Shell icon to open the Cloud Shell pane.
3. At the Cloud Shell command prompt, type in the following command and press Enter to list all resource
groups you created in this lab:
Shell Copy
4. Verify that the output contains only the resource groups you created in this lab. These groups will be
deleted in the next task.
1. At the Cloud Shell command prompt, type in the following command and press Enter to delete the
resource groups you created in this lab
Shell Copy
❕ Result: In this exercise, you removed the resources used in this lab.