From bcbfe731f612f8b70f2b9814764a5c2ed6ff0bd0 Mon Sep 17 00:00:00 2001 From: Clifford Brent Smith <78555251+clifford-smith@users.noreply.github.com> Date: Wed, 10 Feb 2021 16:25:22 -0700 Subject: [PATCH] Update LAB_04-Implement_Virtual_Networking.md --- .../LAB_04-Implement_Virtual_Networking.md | 56 ++++++++++++++++--- 1 file changed, 49 insertions(+), 7 deletions(-) diff --git a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md index ae3b9471..c05b1e1a 100644 --- a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md +++ b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md @@ -45,16 +45,25 @@ In this task, you will create a virtual network with multiple subnets by using t | Resource Group | the name of a **new** resource group **az104-04-rg1** | | Name | **az104-04-vnet1** | | Region | the name of any Azure region available in the subscription you will use in this lab | - | IPv4 address space | **10.40.0.0/20** | - | Subnet name | **subnet0** | - | Subnet address range | **10.40.0.0/24** | +1. Click **Next : IP Addresses** and enter the following values + + | Setting | Value | + | --- | --- | + | IPv4 address space | **10.40.0.0/20** | + +1. Click **+ Add subnet** enter the following values then click **Add** + + | Setting | Value | + | --- | --- | + | Subnet name | **subnet0** | + | Subnet address range | **10.40.0.0/24** | 1. Accept the defaults and click **Review and Create**. Let validation occur, and hit **Create** again to submit your deployment. >**Note:** Wait for the virtual network to be provisioned. This should take less than a minute. -1. Once the deployment completes browse for **Virtual Networks** in the portal search bar. Within **Virtual networks** blade, click on the newly created virtual network **az104-04-vnet1**. +1. Click on **Go to resource** 1. On the **az104-04-vnet1** virtual network blade, click **Subnets** and then click **+ Subnet**. @@ -66,6 +75,8 @@ In this task, you will create a virtual network with multiple subnets by using t | Address range (CIDR block) | **10.40.1.0/24** | | Network security group | **None** | | Route table | **None** | + +1. Click **Save** #### Task 2: Deploy virtual machines into the virtual network @@ -127,7 +138,24 @@ In this task, you will configure static assignment of public and private IP addr 1. Back on the **ipconfig1** blade, save the changes. -1. Navigate back to the **az104-04-vnet1** blade and repeat the previous six steps to change the IP address assignment of **ipconfig1** of **az104-04-nic1** to **Static** and associate **az104-04-nic1** with a new Standard SKU public IP address named **az104-04-pip1**. +1. Navigate back to the **az104-04-vnet1** blade + +1. Click **az104-04-nic1** and, on the **az104-04-nic1** blade, click **IP configurations**. + + >**Note**: Verify that **ipconfig1** is currently set up with a dynamic private IP address. + +1. In the list IP configurations, click **ipconfig1**. + +1. On the **ipconfig1** blade, set **Assignment** to **Static**, leave the default value of **IP address** set to **10.40.1.4**. + +1. On the **ipconfig1** blade, in the **Public IP address settings** section, select **Associate**, click **+ Create new**, specify the following settings, and click **OK**: + + | Setting | Value | + | --- | --- | + | Name | **az104-04-pip1** | + | SKU | **Standard** | + +1. Back on the **ipconfig1** blade, save the changes. 1. Navigate back to the **az104-04-rg1** resource group blade, in the list of its resources, click **az104-04-vm0**, and from the **az104-04-vm0** virtual machine blade, note the public IP address entry. @@ -158,6 +186,8 @@ In this task, you will configure network security groups in order to allow for r | Resource Group | **az104-04-rg1** | | Name | **az104-04-nsg01** | | Region | the name of the Azure region where you deployed all other resources in this lab | + +1. Click **Review and Create**. Let validation occur, and hit **Create** to submit your deployment. >**Note**: Wait for the deployment to complete. This should take about 2 minutes. @@ -211,6 +241,8 @@ In this task, you will configure DNS name resolution within a virtual network by | Subscription | the name of the Azure subscription you are using in this lab | | Resource Group | **az104-04-rg1** | | Name | **contoso.org** | + +1. Click Review and Create. Let validation occur, and hit Create again to submit your deployment. >**Note**: Wait for the private DNS zone to be created. This should take about 2 minutes. @@ -218,7 +250,7 @@ In this task, you will configure DNS name resolution within a virtual network by 1. On the **contoso.org** private DNS zone blade, in the **Settings** section, click **Virtual network links** -1. Add a virtual network link with the following settings (leave others with their default values): +1. Click **+ Add** to create a virtual network link with the following settings (leave others with their default values): | Setting | Value | | --- | --- | @@ -226,6 +258,8 @@ In this task, you will configure DNS name resolution within a virtual network by | Subscription | the name of the Azure subscription you are using in this lab | | Virtual network | **az104-04-vnet1** | | Enable auto registration | enabled | + +1. Click **OK**. >**Note:** Wait for the virtual network link to be created. This should take less than 1 minute. @@ -261,6 +295,8 @@ In this task, you will configure external DNS name resolution by using Azure pub | Subscription | the name of the Azure subscription you are using in this lab | | Resource Group | **az104-04-rg1** | | Name | the DNS domain name you identified earlier in this task | + +1. Click Review and Create. Let validation occur, and hit Create again to submit your deployment. >**Note**: Wait for the DNS zone to be created. This should take about 2 minutes. @@ -278,6 +314,10 @@ In this task, you will configure external DNS name resolution by using Azure pub | TTL | **1** | | TTL unit | **Hours** | | IP address | the public IP address of **az104-04-vm0** which you identified in the third exercise of this lab | + +1. Click **OK** + +1. On the DNS zone blade, click **+ Record set**. 1. Add a record set with the following settings (leave others with their default values): @@ -289,12 +329,14 @@ In this task, you will configure external DNS name resolution by using Azure pub | TTL | **1** | | TTL unit | **Hours** | | IP address | the public IP address of **az104-04-vm1** which you identified in the third exercise of this lab | + +1. Click **OK** 1. On the DNS zone blade, note the name of the **Name server 1** entry. 1. In the Azure portal, open the **PowerShell** session in **Cloud Shell** by clicking on the icon in the top right of the Azure Portal. -1. From the Cloud Shell pane, run the following to test external name resolution of the **az104-04-vm0** DNS record set in the newly created DNS zone **(replace the placeholder `[Name server 1]` including the [] brackets**, with the name of **Name server 1** you noted earlier in this task and the `[domain name] placeholder with the name of the DNS domain you created earlier in this task): +1. From the Cloud Shell pane, run the following to test external name resolution of the **az104-04-vm0** DNS record set in the the newly created DNS zone (replace the placeholder `[Name server 1]` with the name of **Name server 1** you noted earlier in this task and the `[domain name] placeholder with the name of the DNS domain you created earlier in this task): ```powershell nslookup az104-04-vm0.[domain name] [Name server 1]