Lecture 33: Hands on exercises scenarios
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：02:16
- 来源：Udemy Lecture 42951680
- Slide 数量：3
- 画面切换：00:21、01:26
扫描说明
按 Udemy Transcript 的 30 个时间点逐一定位并比较视频画面，确认标题和两个实验拓扑共 3 个 Slide。拓扑组件的逐步出现视为动画构建，截图保留最终稳定状态。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. Hands-on VPC DNS Lab Overview
时间范围：00:00–00:21
总结 / Summary
中文
接下来的实操比较两种 VPC DNS 方案：继续使用 Amazon 提供的 DNS（AmazonProvidedDNS），以及把实例改为使用自建 DNS 服务器（Custom DNS Server）。两种方案都将解析 VPC 内的自定义私有名称。
English
The upcoming hands-on work compares two VPC DNS designs: continuing to use AmazonProvidedDNS and redirecting instances to a custom DNS server. Both designs resolve custom private names inside the VPC.
Transcript
00:00 Hi.
00:00 So with the knowledge that we have, let's do some hands on exercises.
00:04 So we want to try two scenarios where first we use the default Amazon provided DNS server as our DNS
00:12 resolver.
00:13 And second, we want to use our own custom DNS server.
00:17 So for the first scenario the setup will look like this.
2. Scenario 1: Route 53 Resolver and Private Hosted Zone
时间范围：00:21–01:26
总结 / Summary
中文
场景 1 保留 DHCP 选项集（DHCP Option Set）中的 name-servers=AmazonProvidedDNS，把域名设为 corp.internal，并创建同名 Route 53 私有托管区域（Private Hosted Zone）。区域内记录把 app.corp.internal 和 db.corp.internal 映射到实例私有 IP，使应用服务器能按名称访问数据库服务器。
English
Scenario 1 keeps name-servers=AmazonProvidedDNS in the DHCP option set, changes the domain to corp.internal, and creates a Route 53 Private Hosted Zone with the same name. Records map app.corp.internal and db.corp.internal to private instance addresses so the application server can reach the database server by name.
Transcript
00:21 For example, you have VPCs and a couple of EC2 instances.
00:24 And we want to have our custom domain name which is core dot internal.
00:30 And then one of the EC2 instance will be app dot core, dot internal and other one will be DB dot corp
00:36 dot internal.
00:37 And we want to connect to DB dot core, dot internal from the app server using its DNS name.
00:45 Now here our DNS server will be the default DNS server.
00:49 That means in the Dhcp option set we don't need to change the name server.
00:54 However, we can change our domain name from the region dot compute dot internal to core dot internal.
01:03 And then we need to create a route 53 private hosted zone with the same name as core dot internal.
01:08 And then we will create multiple records which points to the private IP addresses of these EC2 instances.
01:16 And that's it.
01:17 Then we should be able to use this internal domain name for the communication between these EC2 instances.
01:23 So that's the first scenario.
3. Scenario 2: Custom DNS Server
时间范围：01:26–02:16
总结 / Summary
中文
场景 2 把 DHCP 选项集（DHCP Option Set）的名称服务器改为自建 DNS 服务器（Custom DNS Server）的私有 IP 10.10.0.25。该服务器维护 corp.internal 区域文件（Zone File）和对应记录，因此 EC2 实例会把所有 DNS 查询发送到自建服务器，而不是 Route 53 解析器（Route 53 Resolver）。
English
Scenario 2 changes the DHCP option set's name server to the custom DNS server at private address 10.10.0.25. That server hosts the corp.internal zone file and records, so EC2 instances send all DNS queries to it instead of the Route 53 Resolver.
Transcript
01:26 And then in the second scenario we want to use our own custom DNS server instead of Amazon provided
01:33 DNS server.
01:34 And the most important part here is to update the Dhcp option set where the name server points to the
01:41 same IP address as our custom DNS server.
01:45 So in this case, the EC2 instance will send all the DNS queries to this custom DNS server.
01:51 And here we will create a zone file for this DNS server, which has the similar record as route 53 private
01:58 hosted zone, where the domain name points to corresponding IP addresses.
02:03 So that's our second exercise.
02:06 So I hope that is clear.
02:07 Now with that, let's get into the hands on mode and try to implement this on our own.
02:13 So let's get started.
整讲总结 / Overall Summary
中文
两个实验使用相同的私有命名目标，却采用不同的解析权威：方案一由 Route 53 私有托管区域（Private Hosted Zone）配合 AmazonProvidedDNS 提供托管解析；方案二通过 DHCP 选项集（DHCP Option Set）把客户端定向到自建 DNS 服务器（Custom DNS Server）。
English
Both labs target the same private naming outcome but use different authorities. The first combines a Route 53 Private Hosted Zone with AmazonProvidedDNS; the second uses the DHCP option set to direct clients to a custom DNS server.
返回顶部 ↑