Study guide

6.2 Azure Traffic Manager & DNS Load Balancing

Designing and Implementing Microsoft Azure Networking Solutions AZ-700

Track your progress as you read

Finished sections get a check mark.

1 Introduction & AZ-700 Exam Overview

0.1 About the AZ-700 Exam: Format, Scoring & Skills Measured

2 Chapter 1: Azure Virtual Networks, Addressing & Subnet Architecture

1.1 VNet Planning, IP Addressing & Subnet Design 1.2 Virtual Network Peering & Global Peering 1.3 Azure NAT Gateway & Outbound Connectivity 1.4 Azure Virtual Network Manager (AVNM) & Network Groups 1.5 Public IP Addresses, Public IP Prefixes & Custom IP Prefixes (BYOIP)

3 Chapter 2: Azure Name Resolution & Core Routing

2.1 Azure DNS & Private DNS Zones 2.2 Azure Private DNS Resolver & Hybrid Name Resolution 2.3 System Routes & User-Defined Routes (UDR) 2.4 BGP & Custom Route Propagation 2.5 Azure Route Server & Dynamic NVA Route Exchange

4 Chapter 3: Hybrid Connectivity with Azure VPN Gateway

3.1 Azure VPN Gateway Architecture & SKUs 3.2 Site-to-Site (S2S) VPN & High Availability 3.3 Point-to-Site (P2S) VPN & Client Authentication 3.4 Azure Extended Network, Always On VPN & Azure Network Adapter

5 Chapter 4: Azure ExpressRoute & Virtual WAN

4.1 Azure ExpressRoute Architecture & Peering Models 4.2 ExpressRoute Routing, Resiliency & Global Reach 4.3 Azure Virtual WAN Architecture & Hub Routing 4.4 ExpressRoute BFD, Monitoring & Connection Troubleshooting

6 Chapter 5: Regional Load Balancing & Application Gateway

5.1 Azure Load Balancer Architecture & Rules 5.2 Azure Application Gateway Architecture & Routing 5.3 Web Application Firewall (WAF) on Application Gateway 5.4 Inbound NAT Rules, Port Forwarding & Health Probe Design

7 Chapter 6: Global Traffic Management & Azure Front Door

6.1 Azure Front Door Architecture & Routing 6.2 Azure Traffic Manager & DNS Load Balancing 6.3 Load Balancing Decision Matrix & Multi-Tier Design 6.4 Web Application Firewall on Azure Front Door

8 Chapter 7: Azure Private Link & Service Endpoints

7.1 Virtual Network Service Endpoints & Policies 7.2 Azure Private Endpoints & Private Link Architecture 7.3 Private Endpoint DNS Integration & Hybrid Resolution 7.4 Azure Private Link Service for Multi-Tenant Solutions

9 Chapter 8: Network Security Groups & Azure Bastion

8.1 Network Security Groups (NSGs) & Application Security Groups (ASGs) 8.2 Azure Bastion Architecture & Secure Remote Access 8.3 Azure Virtual Network Manager Security Admin Rules

10 Chapter 9: Azure Firewall & Security Policies

9.1 Azure Firewall Architecture & Rule Processing 9.2 Azure Firewall Manager & DDoS Protection

11 Chapter 10: Azure Network Observability & Troubleshooting

10.1 Network Watcher Diagnostic Tools 10.2 NSG Flow Logs, VNet Flow Logs & Traffic Analytics 10.3 Network Troubleshooting Scenarios & End-to-End Connectivity 10.4 Azure Monitor Network Insights & Defender for Cloud Network Posture

6.2 Azure Traffic Manager & DNS Load Balancing

Key Takeaways Explain This Topic AI

Azure Traffic Manager operates exclusively at the DNS layer (Layer 4/any protocol), returning optimal endpoint IP addresses to clients without proxying or intercepting the actual data payload.

Traffic Manager supports six routing methods: Priority (active-standby failover), Weighted (traffic splitting/canary), Performance (lowest network latency via IP telemetry), Geographic (regional compliance/data sovereignty), Multivalue (returns up to 8 healthy IPs), and Subnet (routes based on client IP prefix mapping).

Nested Traffic Manager profiles enable multi-tier routing logic by nesting child profiles (e.g., Priority or Performance) beneath a parent profile (e.g., Geographic or Subnet).

Health monitoring probes endpoints via HTTP, HTTPS, or TCP with configurable probe intervals (Standard 30s vs. Fast 10s), probe timeouts (5-10s), and failure thresholds (1-10 tolerated failures).

DNS Time-to-Live (TTL) configuration is a critical operational parameter: lower TTL (e.g., 30s) enables rapid failover at the expense of higher DNS query volume, while higher TTL (e.g., 300s) improves DNS caching performance.

Last updated: August 2026

Azure Traffic Manager & DNS Load Balancing

While Azure Front Door operates as an active Layer 7 reverse proxy, Azure Traffic Manager (ATM) operates at the DNS layer . Traffic Manager uses the global Domain Name System to direct client requests to the most appropriate service endpoint based on sophisticated traffic-routing algorithms and continuous health monitoring.

Because Traffic Manager works strictly at the DNS level, it is completely protocol-agnostic . It can direct traffic for non-HTTP applications, such as multiplayer gaming (UDP), legacy enterprise protocols (TCP), database replication streams, and VPN endpoints, in addition to standard web traffic.

1. How DNS-Based Load Balancing Works

To understand Traffic Manager, you must master the step-by-step DNS resolution lifecycle. Traffic Manager is never in the data path between the client and the application server. Once DNS resolution completes, the client communicates directly with the target endpoint's IP address. +-----------------------------------------------------------------------------+

  • | AZURE TRAFFIC MANAGER DNS RESOLUTION FLOW |
  • | |
  • | 1. Client queries local DNS resolver for 'app.contoso.com' |
  • | 2. Local DNS resolver queries Azure DNS Name Servers for Traffic Manager |
  • | 3. Traffic Manager evaluates routing method + endpoint health status |
  • | 4. Traffic Manager returns IP address (e.g., 20.40.60.80) to DNS resolver |
  • | 5. Local DNS resolver caches IP according to TTL and returns IP to client |
  • | 6. Client connects DIRECTLY to 20.40.60.80 over TCP/UDP/HTTP/HTTPS |
  • | |
  • | [Client] ===================== Direct Data Flow ====================> [Origin]
  • | ^ |
  • | |---- DNS Query/Response (Traffic Manager in Control Plane Only) -----| |
  • +-----------------------------------------------------------------------------+

Key Characteristics of DNS Load Balancing:

No Bandwidth Bottleneck: Because application data packets do not flow through Traffic Manager, there is no throughput limitation, gateway processing overhead, or per-gigabyte data processing fee.

Protocol Independence: Supports any protocol over TCP or UDP (e.g., SSH, RDP, custom socket protocols, RTP audio/video).

Client & Resolver Caching Dependency: Failover speed is governed by the configured DNS TTL and whether intermediate recursive DNS resolvers respect the TTL header.

Loading diagram... Traffic Manager DNS Resolution and Direct Client Communication Flow

2. Deep Dive: The Six Traffic Routing Methods

Azure Traffic Manager provides six distinct routing methods to satisfy diverse availability, performance, geographic compliance, and client-steering requirements. +-----------------------------------------------------------------------------+

  • | TRAFFIC MANAGER ROUTING METHODS SUMMARY |
  • | |
  • | Method Primary Objective Selection Mechanism |
  • | ------------ ------------------------- ---------------------------- |
  • | Priority Active / Passive Failover Lowest priority integer (1..N) |
  • | Weighted Traffic Distribution Proportional weight (1..1000) |
  • | Performance Lowest Network Latency Internet Latency Table Map |
  • | Geographic Data Sovereignty & Geo-Lock DNS query source IP geographic |
  • | Multivalue Client-Side Failover Returns up to 8 healthy IPs |
  • | Subnet Deterministic IP Mapping Client IP subnet CIDR ranges |
  • +-----------------------------------------------------------------------------+
  • 1. Priority Routing (Active / Standby Failover)

Mechanics: Each endpoint is assigned a unique priority integer from 1 to 1000 (1 being highest priority). Traffic Manager always returns the healthy endpoint with the lowest priority number.

Failover Behavior: If Priority 1 fails health checks, Traffic Manager automatically starts returning Priority 2. When Priority 1 recovers, Traffic Manager immediately fails back to Priority 1.

Use Case: Primary datacenter with a warm disaster recovery (DR) site.

2. Weighted Routing (Traffic Splitting & Canary Testing)

Mechanics: Endpoints are assigned an integer weight from 1 to 1000. Traffic Manager distributes DNS responses proportionally based on total weight.

Formula: Percentage = Endpoint Weight ∑ All Healthy Endpoint Weights × 100 % \text{Percentage} = \frac{\text{Endpoint Weight}}{\sum \text{All Healthy Endpoint Weights}} \times 100\% Percentage = ∑ All Healthy Endpoint Weights Endpoint Weight ​ × 100%

Use Case: Blue-green deployments, canary testing new software versions (e.g., 90% traffic to stable version, 10% to new release), and gradual cloud migrations.

3. Performance Routing (Lowest Latency)

Mechanics: Microsoft continuously maintains and updates a global Internet Latency Table tracking round-trip times between global IP address ranges and all Azure datacenters. When a DNS request arrives, Traffic Manager looks up the source IP of the recursive DNS resolver in this table and returns the endpoint offering the lowest network latency.

Use Case: Multi-region deployments where users should always connect to the geographically closest and fastest datacenter.

4. Geographic Routing (Data Sovereignty & Regional Content)

Mechanics: Administrators explicitly map geographic regions (World, Regional Groups, Countries, or US States/Provinces) to specific endpoints. When a DNS query originates from an IP within that geographic territory, Traffic Manager directs it strictly to the assigned endpoint.

Key Behavior: Geographic routing does not fail over across geographic boundaries by default unless configured with a catch-all endpoint ( All (World) ). If an endpoint assigned to Western Europe fails and no fallback is defined, European users receive an unresolvable DNS response ( NXDOMAIN / SERVFAIL ) to prevent accidental violation of data sovereignty laws (e.g., GDPR).

5. Multivalue Routing (Client-Side Load Balancing & Resilience)

Mechanics: Returns up to 8 healthy IPv4 and IPv6 endpoint IP addresses in a single DNS query response.

Client Behavior: The client browser or application receives multiple A/AAAA records and can perform round-robin load balancing or automatically retry alternative IPs if the primary connection fails, without waiting for a new DNS query.

Constraint: Requires endpoints to be configured with static public IP addresses (not FQDNs).

6. Subnet Routing (Deterministic IP Range Mapping)

Mechanics: Administrators map specific client IPv4/IPv6 CIDR prefixes (e.g., corporate headquarters 198.51.100.0/24 , branch offices 203.0.113.0/24 ) to designated endpoints.

Use Case: Directing internal corporate users to dedicated test environments, steering business partners to customized tenant clusters, or enforcing compliance boundaries based on known IP blocks.

3. Nested Traffic Manager Profiles

Complex enterprise architectures frequently require combining multiple routing methods. Azure supports Nested Profiles , where a child Traffic Manager profile is added as an endpoint to a parent Traffic Manager profile. +-----------------------------------------------------------------------------+

  • | NESTED TRAFFIC MANAGER PROFILE TOPOLOGY |
  • | |
  • | [Parent Profile: Geographic Routing] |
  • | - Europe Queries -> Child Profile EU |
  • | - Americas Queries -> Child Profile US |
  • | | |
  • | +-----------------+-----------------+ |
  • | | | |
  • | v v |
  • | [Child Profile EU: Priority] [Child Profile US: Weighted] |
  • | - Primary: West Europe (P1) - Production App: 80% |
  • | - Standby: North Europe (P2) - Canary App: 20% |
  • +-----------------------------------------------------------------------------+

Nested Profile Architecture Guidelines:

Parent Evaluation: The parent profile routes the incoming DNS query based on its top-level routing method (e.g., Geographic or Subnet).

Child Evaluation: The child profile receives the request and applies its own routing method (e.g., Priority failover between regional clusters, or Weighted canary splitting).

Health Aggregation: A child profile is considered healthy by the parent profile only if the minimum configured number of healthy endpoints within that child profile are online.

4. Endpoint Types, Health Monitoring & Probing Architecture

Traffic Manager supports three types of endpoints:

Azure Endpoints: Public IPs, App Services, or Cloud Services hosted within Microsoft Azure.

External Endpoints: On-premises servers, third-party cloud VMs (AWS, GCP), or external IP/FQDNs.

Nested Endpoints: Other Traffic Manager child profiles.

Endpoint Health Probing Mechanics

Traffic Manager monitors endpoint health via distributed probing agents running worldwide.

Health Probe Parameter Supported Values Exam Impact & Operational Significance

Protocol HTTP, HTTPS, TCP HTTP/HTTPS checks for status code 200 OK; TCP checks for successful 3-way handshake on designated port.

Port 1–65535 Target service listening port (e.g., 80, 443, 8080, 3389).

Path URI string (e.g., /healthz ) Applies to HTTP/HTTPS probes. Must return HTTP 200 within timeout window.

Probing Interval Standard (30s) or Fast (10s) Fast probing reduces failover detection time from ~60-90s down to ~20-30s, but increases probe traffic and cost.

Tolerated Number of Failures 1 to 10 (Default: 3) Consecutive probe failures required before an endpoint transitions from Online to Degraded .

Probe Timeout 5 to 10 seconds (Default: 10s) Maximum duration the probing agent waits for an HTTP response or TCP handshake.

Endpoint Status States:

Online : Endpoint is responding successfully to health probes and receiving DNS traffic.

Degraded : Endpoint failed consecutive health probes exceeding the failure threshold; removed from DNS response rotation.

Inactive / Disabled : Administratively disabled by the administrator; no health probes sent and no DNS traffic routed.

5. DNS TTL Tuning & Caching Implications

The DNS Time-to-Live (TTL) setting in Traffic Manager dictates how many seconds a client device or recursive DNS resolver can cache the DNS record before making a fresh query. +-----------------------------------------------------------------------------+

  • | DNS TTL TRADE-OFF MATRIX |
  • | |
  • | Setting Failover Speed DNS Query Volume Resolver Load |
  • | ---------- ------------------ ------------------- --------------- |
  • | Low TTL Fast Failover High Query Volume Higher Cost & |
  • | (10s - 30s) (10 - 60 seconds) (Frequent Lookups) DNS Overhead |
  • | |
  • | High TTL Slow Failover Low Query Volume Optimized Cache & |
  • | (300s+) (5 - 15+ minutes) (Infrequent Lookups) Lower Cost |
  • +-----------------------------------------------------------------------------+

Caution

The Recursive DNS Caching Problem: Even if Traffic Manager TTL is set to 10 seconds, some public ISP DNS resolvers enforce minimum TTL floors (e.g., caching records for 60 to 300 seconds regardless of authority headers). Applications requiring guaranteed, instantaneous sub-second failover should use Azure Front Door (Anycast BGP) rather than DNS-based Traffic Manager.