Study/AZ-104-MicrosoftAzureAdministrator
1
0
Fork 0
mirror of https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator.git synced 2026-02-14 04:47:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update LAB_04-Implement_Virtual_Networking.md

Browse Source
This commit is contained in:
staleycyn 2024-02-02 06:28:04 -08:00 committed by GitHub
parent 7e709d30b8
commit e78756b0f6
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 13 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
New Instructions/Lab/LAB_04-Implement_Virtual_Networking.md
View File

@ -263,7 +263,7 @@ You can configure Azure DNS to resolve host names in your public domain. For exa
| Name | `contoso.com` |
| Region |**East US** (review the informational icon) |
1. Select **Review + create** and then **Create**.
1. Select **Review create** and then **Create**.
1. Wait for the DNS zone to deploy and then select **Go to resource**.
@ -289,11 +289,11 @@ You can configure Azure DNS to resolve host names in your public domain. For exa
```
1. Verify the host name www.contoso.com resolves to the IP address you provided. This confirms name resolution is working correctly.
### Configure a private DNS zone.
### Configure a private DNS zone
A private DNS zone provides name resolution services within virtual networks. A private DNS zone is only accessible from the virtual networks that it is linked to and can't be accessed from the internet.
1. In the portal, search for and select **Private dns zones**.
1. In the portal, search for and select `Private dns zones`.
1. Select **+ Create**.
@ -303,37 +303,35 @@ A private DNS zone provides name resolution services within virtual networks. A
|:---------|:---------|
| Subscription | **Select your subscription** |
| Resource group | **az04-rg4** |
| Name | **contoso.com** |
| Region |**East US** (review the informational icon) |
| Name | `private.contoso.com` |
| Region |**East US** |
1. Select **Review create** and then **Create**.
1. Wait for the DNS zone to deploy and then select **Go to resource**.
1. Notice on the **Overview** blade there are no name server records.
1. Select **+ Virtual network links** and then select **+ Add**.
| Property | Value |
|:---------|:---------|
| Link name | `manu-vnet-link` |
| Link name | `manufacturing-link` |
| Virtual network | `ManufacturingVnet` |
1. Select **OK** and wait for the link to create.
1. From the **Overview** blade select **+ Record set**. You add a virtual network link record for each virtual network that needs private name-resolution support.
1. From the **Overview** blade select **+ Record set**. You would now add a record for each virtual machine that needs private name-resolution support.
| Property | Value |
|:---------|:---------|
| Name | **database** |
| Name | **sensorvm** |
| Type | **A** |
| TTL | **1** |
| IP address | **10.1.1.4** |
>**Note:** In a real-world scenario, you'd enter the IP address for a specific manufacturing virtual machine.
1. Select **OK** and verify **contoso.com** has a record set named **backend**.
## Key takeaways
Congratulations on completing the lab. Here are the main takeaways for this lab.