Update LAB_04-Implement_Virtual_Networking.md

This commit is contained in:
Clifford Brent Smith 2021-02-10 16:25:22 -07:00 committed by GitHub
parent 286d5856a8
commit bcbfe731f6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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** | | Resource Group | the name of a **new** resource group **az104-04-rg1** |
| Name | **az104-04-vnet1** | | Name | **az104-04-vnet1** |
| Region | the name of any Azure region available in the subscription you will use in this lab | | Region | the name of any Azure region available in the subscription you will use in this lab |
1. Click **Next : IP Addresses** and enter the following values
| Setting | Value |
| --- | --- |
| IPv4 address space | **10.40.0.0/20** | | 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 name | **subnet0** |
| Subnet address range | **10.40.0.0/24** | | 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. 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. >**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**. 1. On the **az104-04-vnet1** virtual network blade, click **Subnets** and then click **+ Subnet**.
@ -67,6 +76,8 @@ In this task, you will create a virtual network with multiple subnets by using t
| Network security group | **None** | | Network security group | **None** |
| Route table | **None** | | Route table | **None** |
1. Click **Save**
#### Task 2: Deploy virtual machines into the virtual network #### Task 2: Deploy virtual machines into the virtual network
In this task, you will deploy Azure virtual machines into different subnets of the virtual network by using an ARM template In this task, you will deploy Azure virtual machines into different subnets of the virtual network by using an ARM template
@ -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. 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. 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.
@ -159,6 +187,8 @@ In this task, you will configure network security groups in order to allow for r
| Name | **az104-04-nsg01** | | Name | **az104-04-nsg01** |
| Region | the name of the Azure region where you deployed all other resources in this lab | | 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. >**Note**: Wait for the deployment to complete. This should take about 2 minutes.
1. On the deployment blade, click **Go to resource** to open the **az104-04-nsg01** network security group blade. 1. On the deployment blade, click **Go to resource** to open the **az104-04-nsg01** network security group blade.
@ -212,13 +242,15 @@ In this task, you will configure DNS name resolution within a virtual network by
| Resource Group | **az104-04-rg1** | | Resource Group | **az104-04-rg1** |
| Name | **contoso.org** | | 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. >**Note**: Wait for the private DNS zone to be created. This should take about 2 minutes.
1. Click **Go to resource** to open the **contoso.org** DNS private zone blade. 1. Click **Go to resource** to open the **contoso.org** DNS private zone blade.
1. On the **contoso.org** private DNS zone blade, in the **Settings** section, click **Virtual network links** 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 | | Setting | Value |
| --- | --- | | --- | --- |
@ -227,6 +259,8 @@ In this task, you will configure DNS name resolution within a virtual network by
| Virtual network | **az104-04-vnet1** | | Virtual network | **az104-04-vnet1** |
| Enable auto registration | enabled | | Enable auto registration | enabled |
1. Click **OK**.
>**Note:** Wait for the virtual network link to be created. This should take less than 1 minute. >**Note:** Wait for the virtual network link to be created. This should take less than 1 minute.
1. On the **contoso.org** private DNS zone blade, in the sidebar, click **Overview** 1. On the **contoso.org** private DNS zone blade, in the sidebar, click **Overview**
@ -262,6 +296,8 @@ In this task, you will configure external DNS name resolution by using Azure pub
| Resource Group | **az104-04-rg1** | | Resource Group | **az104-04-rg1** |
| Name | the DNS domain name you identified earlier in this task | | 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. >**Note**: Wait for the DNS zone to be created. This should take about 2 minutes.
1. Click **Go to resource** to open the blade of the newly created DNS zone. 1. Click **Go to resource** to open the blade of the newly created DNS zone.
@ -279,6 +315,10 @@ In this task, you will configure external DNS name resolution by using Azure pub
| TTL unit | **Hours** | | TTL unit | **Hours** |
| IP address | the public IP address of **az104-04-vm0** which you identified in the third exercise of this lab | | 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): 1. Add a record set with the following settings (leave others with their default values):
| Setting | Value | | Setting | Value |
@ -290,11 +330,13 @@ In this task, you will configure external DNS name resolution by using Azure pub
| TTL unit | **Hours** | | TTL unit | **Hours** |
| IP address | the public IP address of **az104-04-vm1** which you identified in the third exercise of this lab | | 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. 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. 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 ```powershell
nslookup az104-04-vm0.[domain name] [Name server 1] nslookup az104-04-vm0.[domain name] [Name server 1]