Virtual Network Peering, Private DNS
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
October 13th, 2023 - Resolved CIDR overlap issue
May 17th, 2023 - Updated screenshots and instructions to reflect the latest UI
David has been a trainer with QA for over 12 years and has been training cloud technologies since 2017. Currently certified in Microsoft and Alibaba cloud technologies David has previously been a system and Network administrator amongst other roles.
Currently, he is a Principle Technology Learning Specialist (Cloud) at QA. He loves nothing more than teaching cloud-based courses and also has a passion for teaching PowerShell scripting.
Outside of work, his main love is flying Radio control airplanes, and teaching people to fly them.