Author: zeusexam

Configure an Azure load balancer As discussed earlier, both internal and public load balancers involve the coordinated configu- ration of several groups of settings. These settings work together to define the overall load balancer behavior. To use Azure Load Balancer, the administrator must first provision the resource, which includes the frontend IP configuration. After this…

Configure load balancing rules Load-balancing rules are used to connect the frontend IP configuration to the back-end server pool, and to a health probe. With Azure Load Balancer, there are no separate back-end HTTP settings configuration; any additional HTTP settings are defined directly within the load- balancing rule itself. These include frontend and back-end ports,…

BACK-END CONFIGURATION The back-end pool defines the back-end servers over which the load balancer will distribute incoming traffic. When using a Basic-tier load balancer, this back-end pool must comprise either a single vir- tual machine, virtual machines in the same availability set, or a VM scale set. If using a VM scale set, traffic will…

Azure Load Balancer The deployment of Azure Load Balancer involves the coordinated configuration of several groups of settings. These settings work together to define the overall Load Balancer behavior. BASIC AND STANDARD LOAD BALANCER TIERS Azure Load Balancer is available in two pricing tiers (SKUs): Basic and Standard. These tiers offer different levels of scale,…

Configure private DNS zones In addition to supporting internet-facing DNS domains, Azure DNS also supports private DNS domains. This provides an alternative approach to name resolution within and between virtual networks. By using private DNS zones, you can use your own custom domain names—including the DNS suffix, rather than the Azure-provided DNS suffix—without the overhead…

Configure custom DNS settings When a virtual machine connects to a virtual network, it receives its IP address via DHCP. As part of that DHCP exchange, DNS settings are also configured in the VM. By default, VMs are configured to use recursive DNS servers in Azure. These provide name resolution for internet- hosted domains, plus…

Alias records Azure DNS offers integration with other services hosted in Azure via alias records. With conventional DNS records, you explicitly specify the target, such as the IP address of an A record. If the IP address changes, you need to update the DNS record accordingly. Using alias records, you can define the target of…

Manage DNS records in Azure DNS Each record in the domain name system includes the following properties: The collection of records in a DNS zone with the same name and the same type is called a resource record set. (These collections are also referred to as “RRSets” and as “record sets” in Azure DNS). Records…

Create and delegate a DNS Zone to Azure DNS A DNS zone is a resource in Azure DNS. Creating a DNS zone resource allocates authorita- tive DNS name servers to host the DNS records for that zone. Azure DNS can then be used to manage those DNS records. DNS queries directed to those DNS name…

DNS services in Azure There are several DNS-related services and features in Azure. An overview of each is given in the following list. The first three items are Azure services, which you consume by creat- ing service-specific resources that you will be billed for. The remaining three items are Azure features, which you configure using…