跟讀練習: Everything You Need to Know About DNS: Crash Course System Design #4 - 通過影片學習英語口語
選擇練習模式
每種模式都會開啟全屏練習室。
81 句
如果句子過短或過長，請點選 Edit 進行調整。
1
DNS or domain name system is the backbone of the internet,
2
but few know exactly how it works.
3
In this video, we'll learn all about the system design of DNS.
4
Let's dive right in.
5
DNS is the internet's directory.
6
It translates human readable domain names such as google.com to machine readable IP addresses.
7
DNS is a little confusing because there are different types of DNS server in the DNS hierarchy,
8
each serving a different purpose.
9
When a browser makes a DNS query,
10
it's asking a DNS resolver.
11
Now this DNS resolver could be from our ISP or from popular DNS providers like Cloudflare's 1.1.1.1 or Google's 8.8.8.8.
12
If the DNS resolver does not have the answer in its cache,
13
it finds the right authoritative nameserver and asks it.
14
The authoritative nameserver is the one that holds the answer.
15
When we update a domain's DNS records as a site owner,
16
we are updating its authoritative nameserver.
17
How does the DNS resolver find the authoritative nameserver?
18
This is where the system of DNS gets interesting.
19
There are three main levels of authoritative DNS servers.
20
There are the root name servers,
21
the top level domain or TLD name servers,
22
and the authoritative name servers for the domains.
23
The root name servers store the IP addresses of the TLD name servers.
24
There are 13 logical root name servers.
25
Each root name server has a single IP address assigned to it.
26
There are actually many physical servers behind each IP address.
27
Through the magic of Anycast,
28
we get routed to the one closest to us.
29
The TLD name servers store the IP addresses of the authoritative name servers for all the domains under them.
30
There are many types of TLD names.
31
We are all familiar with .com, .org, and .edu.
32
There are also country code TLDs like .de and .uk.
33
There are many others.
34
The authoritative nameservers for a domain provide well,
35
authoritative answers to DNS queries.
36
When we register a domain,
37
the registrar hosts the authoritative nameservers by default,
38
but we can change them to others.
39
Cloud providers like AWS and Cloudflare run robust authoritative nameservers.
40
This hierarchical design makes DNS highly decentralized and robust.
41
Now let's walk through the life of a typical DNS query.
42
The user types google.com into the browser.
43
The browser first checks its cache.
44
If it has no answer,
45
it makes an operating system call to try to get the answer.
46
The operating system call would most likely have its own cache too.
47
If the answer isn't there,
48
it reaches out to the DNS resolver.
49
The DNS resolver first checks its cache.
50
If it is not there or if the answer has expired,
51
it asks the root name server.
52
The root name server responds with the list of the .com TLD name servers.
53
Note that since .com is such a common TLD,
54
the resolver most likely already caches the IP addresses for those .com TLD name servers.
55
The DNS resolver then reaches out to the .com TLD name server and the .com TLD name server
56
returns the authoritative name servers for google.com.
57
And finally, the DNS resolver reaches out to google.com's authoritative name server,
58
and it returns the IP addresses of google.com.
59
Now the DNS resolver then returns the IP addresses to the operating system,
60
and the operating system returns them to the browser.
61
Finally, let's go over some gotchas when updating DNS records for a live high traffic production system.
62
DNS propagation is slow because there is a TTL on each DNS record.
63
And some of the default TTLs are pretty long.
64
Also, not every DNS resolver is a good citizen.
65
There are some buggy ones out there that don't honor the TTL.
66
To mitigate the risk, there are two practical steps to take.
67
First, reduce the TTL for the record that we want to change to something very short,
68
say 60 seconds, well in advance before the update actually happens.
69
This gives ample time for all the DNS servers to receive the shortened TTL,
70
which would allow the actual record update to take effect based on the new shortened TTL.
71
Second, leave the server running on the old IP addresses for a while.
72
Only decommission the server when traffic dies down to an acceptable level.
73
Because some DNS resolvers don't honor the TTL,
74
this could take a bit of time and patience.
75
This concludes our video on DNS.
76
We hope you have a better understanding of how its hierarchical design makes it decentralized and robust.
77
Remember, DNS is what translates domain names to IP addresses,
78
making it a critical component of the Internet backbone.
79
You like our videos, you may like our system design newsletter as well.
80
It covers topics and trends in large-scale system design.
81
Trusted by 250,000 readers.
同頻道
C13
Proxy vs Reverse Proxy (Real-world Examples)
Daily ConversationUniversity StudentsWorking Adults
C12
Cache Systems Every Developer Should Know
Daily ConversationUniversity StudentsWorking Adults
C12
Top 5 Redis Use Cases
Daily ConversationUniversity Students
C13
System Design Was HARD - Until You Knew the Trade-Offs
Daily ConversationUniversity StudentsWorking Adults
C12
CAP Theorem Simplified
Daily ConversationUniversity StudentsWorking Adults
C12
What Is REST API? Examples And How To Use It: Crash Course System Design #3
Daily ConversationUniversity StudentsWorking Adults
C18
8 Most Important System Design Concepts You Should Know
Daily ConversationUniversity StudentsWorking Adults
C11
System Design: Why is Kafka fast?
Business EnglishUniversity StudentsWorking Adults
C16
What Are Microservices Really All About? (And When Not To Use It)
Business EnglishUniversity StudentsWorking Adults
C13
How Does a URL Shortener Work?
Business EnglishInterview EnglishUniversity Students
C13
System Design: Why is Kafka Popular?
Business EnglishUniversity StudentsWorking Adults
C11
The Secret Sauce Behind NoSQL: LSM Tree
Daily ConversationUniversity StudentsWorking Adults
C14
What is API Gateway?
Business EnglishUniversity StudentsWorking Adults
C12
10+ Key Memory & Storage Systems: Crash Course System Design #5
University StudentsWorking Adults
C150
Kubernetes Explained in 6 Minutes | k8s Architecture
Business EnglishUniversity StudentsWorking Adults
C24
What Is Redis Really About? Why Is It So Popular?
Business EnglishUniversity StudentsWorking Adults
B2How Git Works: Explained in 4 Minutes
Business EnglishUniversity StudentsWorking Adults
FOR YOU
推薦影片
C11
275 句
Every Networking Concept Explained In 20 Minutes
Daily ConversationUniversity StudentsWorking Adults
C13
173 句
STOP Running Code On Your Computer
Daily ConversationUniversity StudentsWorking Adults
C11
689 句
Database Sharding! Designing Data-Intensive Applications chapter 6
Daily ConversationUniversity StudentsWorking Adults
C11
537 句
Understand Microsoft Entra ID | AZ-104 | Episode 2
Daily ConversationUniversity StudentsWorking Adults
C1231 句
Redis Crash Course - the What, Why and How to use Redis as your primary database
Daily ConversationUniversity StudentsWorking Adults
C1101 句
BGP Overview
Daily ConversationUniversity StudentsWorking Adults
B210
33 句
Crash Course Sex Ed Preview
Daily ConversationUniversity StudentsWorking Adults
C11
9 句
What is a Server? Servers vs Desktops Explained
Daily ConversationUniversity StudentsWorking Adults
C11
74 句
LangChain in 5 Minutes (Explained Clearly)
Daily ConversationUniversity StudentsWorking Adults
C11
54 句
Traceroute: You're Probably Reading the Results Wrong
Daily ConversationUniversity StudentsWorking Adults
為什麼要通過這個影片練習口語？
通過觀看和模仿這段關於DNS的影片，您可以在實際語境中練習英語口語。影片內容涵蓋了網際網路的重要組成部分，使您在掌握技術術語的同時，提升了語言能力。您不僅僅是在學習單詞，還在理解如何將人類可讀的域名轉換為機器可讀的IP地址。這個過程會幫助您在雅思口語練習中，流利地表述有關技術話題，以增強您的自信心和表達能力。
語法與表達在語境中的應用
- “DNS is the backbone of the internet” - 這句話展示了一個常見的主謂結構，強調了DNS的重要性。學習這種結構可以幫助您在描述系統或概念時更加清晰。
- “When a browser makes a DNS query” - 這種條件句的使用非常普遍，能幫助您在複雜的句子中保持邏輯的清晰性。
- “This hierarchical design makes DNS highly decentralized” - 通過理解名詞短語和形容詞的搭配，您可以更好地描述事物的特點和功能。
在這個影片中，快速對比不同型別的DNS伺服器的句子也能激發您在討論技術時使用更復雜的結構。
常見的發音陷阱
在影片中，有些詞彙的發音可能會讓學習者感到困惑。例如，“authoritative”這個詞的重音位置常常會被忽視，它應當強調在第三個音節上。此外，“resolver”的發音對於一些非母語學習者也可能具有挑戰性。為了克服這些發音難點，建議您重複影片中的句子，並注意語音的變化和語調，這對提高您的聽力和口語都會有很大幫助。
結合這些技巧與“看YouTube學英語”的方法，您可以創造一個理想的學習氛圍，利用shadowspeaks和shadowing site等技巧，推動您的英語口語能力邁上新臺階。通過持續的練習，您將能夠更自如地參與到技術性的對話中，使您在雅思口語練習過程中脫穎而出。
什麼是跟讀法？
跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧，最初開發用於專業口譯員的培訓，並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大：您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同，跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性，語調，節奏，連讀，聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。