网络课程笔记

Lecture 203: Routing Policy - Latency

• 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
• 视频时长：04:40
• 来源：Udemy Lecture 28556405
• Slide 数量：6
• 画面切换：00:55、01:40、02:20、03:10、03:55

扫描说明

按时间轴扫描了全长约 04:39 的实际视频，并依据 Latency Routing 原理、创建 Record、Singapore 配置、三 Region 配置、本地解析、VPN 异地验证划分为 6 个小节。Udemy 为本讲错误绑定了上一讲 Weighted Routing 的 125 条 Transcript cue；同时检查页面侧栏与已加载 VTT 后确认两者都不属于本讲，因此没有把错误字幕冒充为本讲原文，而是根据实际画面建立 6 条可审计的 Visual Reconstruction 提纲。截图均在播放器控件隐藏后复核，统一为 1364×770。

⚠️ Udemy 当前为本讲错误绑定了 Lecture 202 的 Weighted Routing 英文 Transcript/VTT。下面不是逐字字幕，而是依据本讲实际视频画面按时间点复原的英文提纲，每条均以 [Visual reconstruction] 标记。

1. Latency-based Routing 返回对用户延迟最低的 Region

时间范围：00:00–00:55

总结 / Summary

中文

Latency-based Routing 的目标是把 DNS Query 指向对该 User 延迟最低的 AWS Region，适合把响应时间作为首要目标的 Global Application。Route 53 使用其掌握的 User-to-Region 网络延迟数据，而不是简单按地理距离判断；因此德国 User 在某些情况下也可能被引导到美国。记录可以与 Health Check 结合。

English

Latency-based routing returns the record for the AWS Region that offers the lowest latency to the user, making it useful for global applications where response time is the priority. Route 53 uses observed user-to-region network latency rather than simple geographic distance, so even a German user could be directed to the United States. Records can also use health checks.

2. 创建同名 A Record 并选择 Latency Policy

时间范围：00:55–01:40

总结 / Summary

中文

在 Hosted Zone 中创建 latency.stephanetheteacher.com，Record Type 选 A，并填入对应 EC2 的 Public IP。把 Routing Policy 从 Simple 改为 Latency 后，控制台会要求指定 Region、可选 Health Check 和唯一的 Record ID。与 Weighted 一样，多 Region 需要多条同名同 Type Record，而不是一条 Record 中塞多个 Value。

English

In the hosted zone, create latency.stephanetheteacher.com as an A record using the corresponding EC2 public IP. Selecting the Latency routing policy makes the console request a region, an optional health check, and a unique record ID. As with weighted routing, multiple regions require separate same-name, same-type records rather than multiple values in one record.

3. 为 Singapore Endpoint 显式指定 ap-southeast-1

时间范围：01:40–02:20

总结 / Summary

中文

第一条 Latency Record 使用 Singapore EC2 IP 54.251.92.166，Region 选择 Asia Pacific (Singapore)，Record ID 标为 ap。Region 字段是 Route 53 进行 Latency Comparison 的关键元数据；它描述 Resource 所在 Region，而不是当前操作者或 DNS Client 的位置。

English

The first latency record uses the Singapore EC2 address 54.251.92.166, selects Asia Pacific (Singapore), and uses ap as the record ID. The region field is the metadata Route 53 needs for latency comparison; it describes the resource's region, not the operator's or DNS client's current location.

4. 为 N. Virginia 与 Frankfurt 创建各自 Region Record

时间范围：02:20–03:10

总结 / Summary

中文

继续为同一个 Hostname 创建 us-east-1 与 eu-central-1 Record，各自填入该 Region 的 EC2 IP、选择 US East (N. Virginia) 或 Europe (Frankfurt)，并设置清晰的 Record ID。三条 Record 可使用相同 TTL；Route 53 在收到 Query 时从这些 Regional Endpoint 中选择预期 Latency 最低且健康的答案。

English

Create additional records for us-east-1 and eu-central-1 using each region's EC2 address, selecting US East (N. Virginia) or Europe (Frankfurt) and assigning clear record IDs. The three records can share a TTL. Route 53 chooses the expected lowest-latency healthy regional endpoint when answering a query.

5. 当前网络解析到 Frankfurt，并返回 eu-central-1c

时间范围：03:10–03:55

总结 / Summary

中文

从讲师当前网络执行 dig，latency Hostname 返回 Frankfurt IP 3.70.14.253；浏览器访问同一域名显示 eu-central-1c。这个结果不是固定绑定或 Round Robin，而是 Route 53 根据当前 DNS Resolver/User 路径的 Latency 数据选择 Europe (Frankfurt) Record，并受 TTL 缓存影响。

English

From the instructor's current network, dig returns the Frankfurt address 3.70.14.253 for the latency hostname, and the browser displays eu-central-1c. This is neither a fixed binding nor round robin; Route 53 chooses the Europe (Frankfurt) record from its latency data for the current DNS resolver and user path, subject to TTL caching.

6. VPN 切到 Hong Kong 后，同一域名改选 Singapore

时间范围：03:55–04:40

总结 / Summary

中文

为模拟亚洲 User，讲师通过 VPN 把客户端出口位置切换到 Hong Kong，再访问同一个 latency Hostname。页面改为返回 ap-southeast-1b，直观验证同一 DNS Name 会随 Client/Resolver 网络位置选择不同 Region。测试时要等待 TTL 过期，并注意实际判断依赖 DNS Resolver 位置与 AWS 延迟测量，而非浏览器 GPS。

English

To simulate an Asian user, the instructor changes the client's egress location to Hong Kong through a VPN and revisits the same latency hostname. The response changes to ap-southeast-1b, showing that one DNS name can select different regions based on the client or resolver network location. Testing must account for TTL expiry, and the decision uses resolver location and AWS latency measurements rather than browser GPS.

整讲总结 / Overall Summary

中文

Latency-based Routing 为每个 Regional Endpoint 创建同名同 Type 的独立 Record，并用 Region 元数据让 Route 53 返回预期网络延迟最低的健康答案。演示中原网络命中 Frankfurt，VPN 切到 Hong Kong 后命中 Singapore，说明它依据网络延迟与 Resolver 位置动态选择，而非纯地理距离或固定轮询。

English

Latency-based routing creates separate same-name, same-type records for regional endpoints and uses region metadata so Route 53 can return the healthy answer with the lowest expected network latency. The demo reaches Frankfurt from the original network and Singapore after switching to Hong Kong via VPN, demonstrating dynamic selection based on latency and resolver location rather than pure distance or fixed rotation.