hands-on lab

Virtual Network Peering, Private DNS

Difficulty: Beginner

Duration: Up to 1 hour and 30 minutes

Students: 320

Rating: 4.2/5

Start lab

Get guided in a real environmentPractice with a step-by-step scenario in a real, provisioned environment.

Learn and validateUse validations to check your solutions every step of the way.

See resultsTrack your knowledge and monitor your progress.

Description

Introduction:

All virtual machines in a single network can communicate with each other, and have Azure's DNS private name resolution by default. This is regardless of how many subnets are in the network. Moving Virtual Machines between subnets within the same network is easily achieved by changing the IP Configuration settings on the Network Adapter (Connected Device).

However, moving Virtual Machines between networks that are located in the same region becomes a little more complex. Also if you want those machines to then communicate with each other, you need to Peer connect the networks together, and provide a Private DNS service for name resolution.

In this Lab exercise, you will:

Start with a pre-existing virtual network (Vnet1), that has a single subnet (Subnet1) with two Virtual Machines connected (TestVM1, TestVM2). Then, you will complete the below tasks.

Test connectivity between TestVM1 and TestVM2 in the existing network
Provision a second virtual network in the same region (Vnet2)
Activate a Bastion Host for remote connectivity to the new network
Move (TestVM2) into the new network
Peer connect the network together
Provide a Private DNS Services and connect it to the networks for name resolution
Test the solution on completion

Start Completion