User-Defined Routes 2 – Virtual Networking

User-Defined Routes 2 – Virtual Networking

Creating a Custom Route 7. After confirming the details, you can click OK, and the route will be added to the Routes blade of the routing table. In short, this route will be applied to the private subnet with the address range 172.17.3.0/24, and all 

User-Defined Routes – Virtual Networking

User-Defined Routes – Virtual Networking

Using system routes, Azure automatically handles all packet routing. As mentioned earlier, users can always override these routes using user-defined routes (UDRs). To give an example of routing, assume we have three subnets inside a virtual network. The subnets are the public subnet, DMZ subnet, 

Service Endpoints – Virtual Networking

Service Endpoints – Virtual Networking

The identity of a virtual network can be provided to the Azure service by using service endpoints. Many services support virtual network access, and with the service endpoint enabled, you can access these services in a secure manner. The communication from your virtual network to 

Private Endpoint – Virtual Networking

Private Endpoint – Virtual Networking

By implementing private endpoints, Azure PaaS services will get a private IP address on your virtual network. As the service is assigned with a private IP address, whenever you send traffic to a PaaS resource, the traffic always stays within your virtual network. Private endpoints 

Azure DNS – Virtual Networking

Azure DNS – Virtual Networking

We are familiar with the DNS servers that we used to administer on-premises. Some organizations used Windows Server as the server for hosting DNS zones, while others used BIND-based solutions. There are other third party-solutions that are used to manage DNS zones and records. In 

Record Management – Virtual Networking

Record Management – Virtual Networking

Azure DNS supports all common DNS record types including A, AAAA, MX, CAA, CNAME, PTR, SOA, SRV, and TXT records. You are familiar with these records as they are used in traditional DNS servers as well. The categorization is done based on the data stored 

Private DNS Zones 2 – Virtual Networking

Private DNS Zones 2 – Virtual Networking

This proves that the virtual network link added to the private zone is working and the virtual machine is using the private DNS zone for name resolution. You can create another VM in the same virtual network, and the record will get automatically registered to 

Private DNS Zones – Virtual Networking

Private DNS Zones – Virtual Networking

As mentioned earlier, Azure DNS can be used to provide name resolution using the Microsoft infrastructure. In Exercise 3.7 and Exercise 3.8, you created a zone and added records for query validation. The zone we hosted in that exercise is an Internet-facing DNS zone because 

Network Security Groups – Virtual Networking

Network Security Groups – Virtual Networking

In quite simple terms, network security groups are a functionality in Azure used to filter and limit inbound and outbound traffic; in other words, they are similar to firewalls. An NSG is a collection of security rules that can be used to allow or deny