AWS · Advanced Networking Specialty

网络课程笔记

Lecture 197 · 5 张幻灯片

幻灯片、双语总结及 Transcript · 图片已内嵌,可离线阅读。

原文默认收起
lecture-197.md

Lecture 197: Route 53 - Creating Our First Records

  • 课程:[NEW] AWS Certified Advanced Networking Specialty 2026
  • 视频时长:03:56
  • 来源:Udemy Lecture 28556383
  • Slide 数量:5
  • 画面切换:01:06、01:42、02:39、03:01

扫描说明

逐条读取了 Udemy 页面中的 101 条英文 Transcript cue,并按时间轴扫描全长约 03:56 的 Hands-on。依据 A Record 创建、Hosted Zone 结果与浏览器失败、CloudShell/bind-utils、nslookup 验证、dig Answer/TTL 验证划分为 5 个小节。截图均在 Transcript 侧栏关闭、播放器控件隐藏后复核,统一为 1364×770。

Transcript 来自 Udemy 页面自带的英文自动字幕,没有使用 ASR。下面保留页面原文,包括其中的语法或识别错误。

1. 创建 test 子域的 Simple A Record

时间范围:00:00–01:06

Route 53 quick-create form for a simple A record with TTL 300

总结 / Summary

中文

进入 Public Hosted Zone 并选择 Create Record。Record Name 填 test,组成 test.stephanetheteacher.com;Type 选 A,Value 使用示例 IPv4 11.22.33.44,TTL 设为 300 Seconds,Routing Policy 保持 Simple。该地址仅用于展示解析,并不对应讲师拥有的真实 Server。

English

Open the public hosted zone and choose Create Record. Enter test to form test.stephanetheteacher.com, select type A, use the sample IPv4 value 11.22.33.44, set TTL to 300 seconds, and keep the simple routing policy. The address only demonstrates resolution and does not belong to a real instructor-owned server.

Transcript

00:00 So now let's go ahead

00:01 and create our first records in Route 53.

00:04 So I'm going to go into my hosted zone,

00:06 and in there I'm going to create some simple records.

00:09 So let's have a look.

00:10 We're going to create a record by clicking on here.

00:13 And in here, I can just have a record name.

00:15 So we want it to be test.stephanetheteacher.com.

00:19 But you can enter anything you want here.

00:21 This is how you would create your domain names.

00:23 Now you have to specify the record type.

00:25 So you can see there's a lot of record types in here,

00:28 but for now we'll keep it simple.

00:29 We'll keep it as an A record.

00:31 And which is to route an IPv4 address

00:34 into a domain name, to an IPv4 address.

00:36 So the answer is going to be

00:38 value is 1, 1, dot, 2, 2, dot, 3, 3, dot, four four.

00:42 Which is just a value we want to have,

00:44 and this is not a domain, an IP we own right now,

00:46 but just to show you just a random value.

00:48 Later on, we'll be routing to a real institute instance.

00:52 Okay.

00:53 TTL is time to live.

00:54 We'll leave it as 300 seconds right now.

00:55 And the routing policy will

00:57 routing policy will have a look at it later on as well.

00:59 We'll leave everything as simple routing. Okay.

01:02 So let's go ahead and create this record.

2. Record 创建成功不代表目标 Web Server 可访问

时间范围:01:06–01:42

Hosted zone listing the newly created test A record

总结 / Summary

中文

创建后 Hosted Zone 中出现 test… A → 11.22.33.44。DNS Query 会正确返回该值,但浏览器打开名称仍失败,因为这个 IP 没有可用 Web Server。DNS 只负责 Name-to-Value Resolution,不会验证应用端口、路由或服务器内容;后续实验才会指向真实 EC2。

English

After creation, the hosted zone lists test… A to 11.22.33.44. DNS queries return that value correctly, but a browser still fails because no usable web server exists at the IP. DNS only resolves names to values; it does not validate application ports, routing, or server content. A later lab points the name to a real EC2 instance.

Transcript

01:06 And now my record has been successfully created.

01:08 So the idea is that if I go to test.stephanetheteacher.com,

01:12 it is going to ask my host zone.

01:16 What is the value of that? And those isn't going to say,

01:18 well, the value of it is 1, 1, dot, 2, 2, dot,

01:21 3, 3, dot, 4, 4.

01:22 So if you try it to do it with a web browser,

01:24 so if you take your browser and you open it

01:27 and you press enter,

01:28 and it's not going to show you many things,

01:30 because right now we don't have 11.22.33.44,

01:34 there's probably no server that exists with that IP as well.

01:38 And if I try to just access this URL,

01:40 it doesn't work. Okay.

3. 在 CloudShell 安装 bind-utils 获取查询命令

时间范围:01:42–02:39

AWS CloudShell installing bind-utils for nslookup and dig

总结 / Summary

中文

可用本地 Windows/macOS Terminal,也可打开 AWS CloudShell 获得统一 Linux CLI。CloudShell 初始可能没有 nslookup 与 dig,因此执行 sudo yum install -y bind-utils 安装相关工具。命令行查询能直接观察 DNS Answer、Record Type 和 TTL,比浏览器更适合验证解析本身。

English

Use a local Windows or macOS terminal, or open AWS CloudShell for a common Linux CLI. CloudShell may initially lack nslookup and dig, so install them with sudo yum install -y bind-utils. Command-line queries expose DNS answers, record types, and TTLs directly, making them better than a browser for validating resolution itself.

Transcript

01:42 So what we know is what is going on behind the scenes.

01:44 And so for this, we're going to type some command lines.

01:46 Now you can be using your command line

01:48 on your windows laptop, or your Mac,

01:50 but because I want everyone to follow the same way as me,

01:53 I'm going to show you how to do it using

01:54 the CloudTrail environments in AWS.

01:57 So let me open the management console,

01:59 and then I'm going to click here to open cloud shell and

02:03 cloud shell is going to allow me to do some commands using

02:06 a standard Linux command line interface. Okay.

02:09 But this is fine,

02:10 if you want to just do it with your own terminal on windows

02:12 or on Mac.

02:14 Okay. So my terminal is not ready.

02:16 And if you're on windows,

02:17 the NS lookup command is going to work. If you're on Mac,

02:20 the dig command is going to work as well.

02:22 But as you can see, these commands are not found

02:24 on my cloud shell.

02:26 So I need you to install them.

02:26 So I do sudo yum, and then install

02:30 minus Y and then bind

02:32 minus utils.

02:34 And it's going to install both VNS lookup

02:36 and the dig commands on my cloud shell.

4. nslookup 返回 A Record 的 11.22.33.44

时间范围:02:39–03:01

Route 53 hosted zone record used by nslookup to resolve the test name

总结 / Summary

中文

运行 nslookup test.stephanetheteacher.com,Resolver 返回 11.22.33.44,与 Hosted Zone 中的 A Record 完全一致。若结果不同,应先检查拼写、Zone Delegation、Record Name 和 Cache;讲师演示中也出现了一次 Domain Typo,说明命令验证时应格外注意 FQDN。

English

Run nslookup test.stephanetheteacher.com and the resolver returns 11.22.33.44, matching the hosted-zone A record. If the result differs, first check spelling, zone delegation, record name, and cache. The instructor also makes a domain typo during the demo, illustrating why exact FQDN input matters.

Transcript

02:39 So lets clear the screen.

02:41 And now let's try to do NS lookup,

02:44 test.stephanietheteacher.com.

02:48 And as you can see, I get an answer,

02:51 which is at test.stephanietheteacher.com,

02:54 is going to 11.22.33.44,

02:56 which is corresponding to what is happening right here,

03:00 which is cool.

5. dig 的 Answer Section 同时展示 Type、TTL 与 Value

时间范围:03:01–03:56

dig output showing the A record TTL and 11.22.33.44 answer

总结 / Summary

中文

运行 dig test.stephanetheteacher.com 后,Answer Section 显示 FQDN、剩余 TTL、IN A 和 11.22.33.44。相比 nslookup,dig 更清晰地展示 DNS Protocol 细节,可用于观察 Cache 后 TTL 递减、确认查询类型,并区分 Answer、Authority 与 Additional Section。

English

Running dig test.stephanetheteacher.com shows the FQDN, remaining TTL, IN A type, and 11.22.33.44 in the answer section. Compared with nslookup, dig exposes DNS protocol details more clearly, making it useful for watching cached TTL decrease, confirming query type, and distinguishing answer, authority, and additional sections.

Transcript

03:01 And I presented like the dig command a little bit more

03:04 because I'm more familiar with it,

03:05 but if you type dig and then the URL that you have,

03:08 okay.

03:09 And press enter,

03:11 you're going to see that and have the wrong commands.

03:14 So stefantheteacher.com,

03:16 so let's clear this screen and then retype the comments.

03:19 Okay.

03:20 Well here, we're going to see

03:21 is that we have the answer section

03:24 and says, test.stephanetheteacher.com is an a record,

03:29 and this is the value of the record. So I like it better,

03:31 better, because it shows you the TTL, as we'll see later on,

03:34 and also shows you the a record,

03:36 the fact that isn't a record. Okay.

03:39 So we have created our first route 53 record,

03:42 and we have been able to query it using a terminal,

03:44 which is cool.

03:45 Obviously loading it from a webpage doesn't work right now,

03:49 but we'll see how we can do it later on

03:51 when we have a real server.

03:53 So I hope you liked this lecture

03:54 and I will see you in the next lecture.

整讲总结 / Overall Summary

中文

本讲在 Route 53 创建 Simple A Record test… → 11.22.33.44,TTL 为 300 秒。DNS 解析成功不等于 Web 应用可用;应使用 nslookup 或 dig 验证 Record 本身,CloudShell 可通过 bind-utils 获得工具。dig 还能直接显示 Record Type、Value 与剩余 TTL。

English

The lecture creates a simple Route 53 A record test… to 11.22.33.44 with a 300-second TTL. Successful DNS resolution does not imply a working web application. Validate the record with nslookup or dig, installing bind-utils in CloudShell if needed. dig also shows the record type, value, and remaining TTL directly.

返回顶部 ↑