Task Statement 2.3: Implement complex hybrid and multi-account DNS architectures.
📘AWS Certified Advanced Networking – Specialty
Traffic Management Using DNS
Traffic management in DNS is about controlling how user requests are routed to different resources (like servers, endpoints, or regions) based on specific rules. This ensures high availability, low latency, and optimized resource use. AWS uses Route 53 for DNS-based traffic management.
For the exam, you need to know types of DNS routing policies, how they work, and when to use them.
1. Routing Policies in AWS Route 53
a) Simple Routing
- What it does: Sends all traffic to a single resource.
- Use case: When you have one server or endpoint serving requests.
- Exam tip: Think of it as the default DNS behavior — no traffic management, just a direct mapping of a domain to an IP or resource.
b) Weighted Routing
- What it does: Distributes traffic across multiple resources based on weight percentages you assign.
- Example in IT terms: You have 2 web servers:
- Server A: 70% of traffic
- Server B: 30% of traffic
Route 53 will send 70% of users to A, 30% to B.
- Use case:
- Gradual migration or testing a new application version.
- Load balancing traffic without using a traditional load balancer.
- Exam tip: Weighted routing can also be used for failover if a resource becomes unhealthy.
c) Latency-Based Routing
- What it does: Routes traffic to the resource with the lowest latency from the user’s location.
- Example in IT terms: You have web servers in US-East and EU-West.
A user in Germany will automatically go to EU-West, because it’s faster than US-East. - Use case: Improving user experience by minimizing response times.
- Exam tip: Route 53 calculates latency per AWS region, not per individual user.
d) Geolocation Routing
- What it does: Sends traffic based on the user’s geographic location (continent, country, or state).
- Example in IT terms: You serve different content for EU and US users.
- Users in EU go to EU servers
- Users in US go to US servers
- Use case:
- Regulatory compliance (GDPR in Europe)
- Delivering localized content
- Exam tip: Route 53 falls back to default record if the user’s location doesn’t match any geolocation rule.
e) Geoproximity Routing (with Traffic Flow)
- What it does: Similar to geolocation, but can shift traffic toward or away from resources based on a bias value.
- Use case in IT terms:
- You want 70% of traffic from India to go to APAC servers, even if EU servers are closer.
- Useful for capacity management.
- Exam tip: Requires AWS Route 53 Traffic Flow and latency calculation. It’s more advanced than geolocation routing.
f) Failover Routing
- What it does: Sends traffic to a primary resource, but automatically switches to a secondary resource if the primary fails.
- Example in IT terms:
- Primary: US-East web server
- Secondary: US-West backup server
If the primary becomes unhealthy, users are routed to the secondary.
- Use case: Disaster recovery and high availability.
- Exam tip: You need to define health checks in Route 53 for this to work.
g) Multi-Value Answer Routing
- What it does: Returns multiple healthy IP addresses for a single DNS query.
- Example in IT terms:
- You have 3 web servers
- Route 53 returns 2 healthy servers randomly for DNS resolution
- Use case: Basic load balancing with DNS-level health checks.
- Exam tip: Works like a combination of simple routing and health checks.
2. Health Checks in Route 53
- Health checks are monitoring tools that check if your resource is available and healthy.
- Can be used with:
- Failover routing
- Weighted routing (to stop sending traffic to unhealthy endpoints)
- Multi-value answer routing
- Exam tip: Health checks are optional for most routing policies but mandatory for failover.
3. Combining Policies Using Traffic Flow
- AWS Route 53 Traffic Flow allows combining routing policies into a single traffic management plan.
- Example:
- Latency-based routing between regions
- Weighted routing within the region
- Failover for backup servers
- Exam tip: Traffic Flow uses traffic policies and policy records.
4. Key Exam Points
- Understand differences between routing policies – don’t confuse weighted with latency or geolocation.
- Know which policy needs health checks – failover and multi-value answer.
- Latency vs geolocation – latency chooses fastest endpoint, geolocation chooses based on user location regardless of latency.
- Weighted routing can be used for gradual deployment.
- Traffic Flow allows complex combinations of multiple routing policies.
- Route 53 is global, so routing policies operate across AWS regions.
Summary Table for Exam
| Routing Policy | Key Feature | Exam Tip |
|---|---|---|
| Simple | Single resource | Default behavior |
| Weighted | Traffic split by weight | Can combine with failover |
| Latency-based | Sends traffic to fastest region | Per AWS region, not per user |
| Geolocation | Based on user location | Fallback to default |
| Geoproximity | Shift traffic using bias | Advanced, needs Traffic Flow |
| Failover | Primary → secondary if unhealthy | Health check required |
| Multi-value Answer | Returns multiple healthy endpoints | Basic load balancing |
