Shadowing Practice: Everything You Need to Know About DNS: Crash Course System Design #4 - Learn English Speaking with Video
Bir pratik modu seçin
Her mod tam ekran bir pratik odası açar.
81 cümleler
Cümleler çok kısa veya çok uzun ise, ayarlamak için Düzenle'ye tıklayın.
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.
Uygulamayı İndir
Akıcı konuşmak için ihtiyacınız olan her şey
AI TelaffuzHer cümleyi puanla
IPA AlıştırmasıHer sesi ustalaştır
Kelime BilgisiKelime bankanızı oluşturun
Kelime OyunuOynarken öğrenin
📺 Aynı Kanal
C11
Top 5 Redis Use Cases
Daily ConversationUniversity Students
C11
The Secret Sauce Behind NoSQL: LSM Tree
Daily ConversationUniversity StudentsWorking Adults
C13
Proxy vs Reverse Proxy (Real-world Examples)
Daily ConversationUniversity StudentsWorking Adults
C12
Cache Systems Every Developer Should Know
Daily ConversationUniversity StudentsWorking Adults
C13
System Design Was HARD - Until You Knew the Trade-Offs
Daily ConversationUniversity StudentsWorking Adults
C17
8 Most Important System Design Concepts You Should Know
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
C12
System Design: Why is Kafka Popular?
Business EnglishUniversity 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
What is API Gateway?
Business EnglishUniversity StudentsWorking Adults
C12
10+ Key Memory & Storage Systems: Crash Course System Design #5
University StudentsWorking Adults
C24
What Is Redis Really About? Why Is It So Popular?
Business EnglishUniversity StudentsWorking Adults
C148
Kubernetes Explained in 6 Minutes | k8s Architecture
Business EnglishUniversity StudentsWorking Adults
C13
How Does a URL Shortener Work?
Business EnglishInterview EnglishUniversity Students
B2How Git Works: Explained in 4 Minutes
Business EnglishUniversity StudentsWorking Adults
✨ Video Öner
C11
275 cümleler
Every Networking Concept Explained In 20 Minutes
Daily ConversationUniversity StudentsWorking Adults
C13
173 cümleler
STOP Running Code On Your Computer
Daily ConversationUniversity StudentsWorking Adults
C11
689 cümleler
Database Sharding! Designing Data-Intensive Applications chapter 6
Daily ConversationUniversity StudentsWorking Adults
C11
537 cümleler
Understand Microsoft Entra ID | AZ-104 | Episode 2
Daily ConversationUniversity StudentsWorking Adults
C1231 cümleler
Redis Crash Course - the What, Why and How to use Redis as your primary database
Daily ConversationUniversity StudentsWorking Adults
C11
781 cümleler
How Do I Reverse Brain Rot?
Daily ConversationUniversity StudentsWorking Adults
C1101 cümleler
BGP Overview
Daily ConversationUniversity StudentsWorking Adults
B210
33 cümleler
Crash Course Sex Ed Preview
Daily ConversationUniversity StudentsWorking Adults
B11
5 cümleler
What is DNA and How Does it Work?
Daily ConversationUniversity StudentsWorking Adults
C11
9 cümleler
What is a Server? Servers vs Desktops Explained
Daily ConversationUniversity StudentsWorking Adults
Bu dersin kelimeleri ve konuşma notları
Bu C1 seviyesindeki konuşma dersi “Everything You Need to Know About DNS: Crash Course System Design” videosuna dayanıyor. En çok tekrarlanan kelimeler: Dns, server, authoritative, resolver, Tld. Bu videoda gölgeleme çalışması için 81 cümle ve 794 kelime var. Konuşma bölümü 5:29 sürüyor. Konuşmacı dakikada yaklaşık 145 kelimelik dengeli bir hızla konuşuyor; gölgeleme için rahat bir tempo. Kelimelerin yalnızca %69’i İngilizcede en sık kullanılan 3.000 kelime arasında, bu yüzden kelime dağarcığı zorlayıcı.
Bu videodaki önemli kelimeler
Videodaki en ileri düzey 13 kelime, telaffuzu ve anlamıyla:
| Kelime | Telaffuz | Anlam |
|---|---|---|
| cache isim | /kæʃ/ | önbellek |
| query isim | /ˈkwɪɹ.i/ | sorgulama |
| hierarchical sıfat | /ˌhaɪəˈɹɑːkɪkəl/ | hiyerarşik |
| backbone isim | /ˈbækˌboʊn/ | omurga |
| translate fiil | /tɹænzˈleɪt/ | tercüme etmek, terceme |
| decommission fiil | /diːkəˈmɪʃən/ | devreden çıkarmak |
| gotcha | /ˈɡɑ.tʃə/ | yakaladım |
| mitigate fiil | /ˈmɪt.ɪ.ɡeɪt/ | azaltmak, dindirmek |
| confuse fiil | /kənˈfjuːz/ | karıştırmak |
| newsletter isim | /ˈn(j)uzˌlɛtɚ/ | haber bülteni |
| hierarchy isim | /ˈhaɪ.ə.ɹɑː(ɹ).ki/ | hiyerarşi |
| conclude fiil | /kənˈkluːd/ | bitirmek |
| directory isim | /dɪˈɹɛktəɹi/ | dizin, klasör |
Dikkat edilecek telaffuzlar
Konuşmacı don't, isn't, we'll gibi kısaltılmış biçimleri 4 kez kullanıyor. Bunları duyduğunuz gibi kısa söyleyin.
- “sh” ve “zh” sesleri: cache /kæʃ/, shorten /ˈʃɔɹtn̩/, decommission /diːkəˈmɪʃən/, propagation /pɹɑpəˈɡeɪʃən/
- Uzun kelimeler — vurguyu doğru yere koyun: authoritative /əˈθɔɹɪˌteɪtɪv/, decentralize /diːˈsɛntɹəlaɪz/, hierarchical /ˌhaɪəˈɹɑːkɪkəl/, decommission /diːkəˈmɪʃən/, propagation /pɹɑpəˈɡeɪʃən/
Türkçe konuşanların zorlandığı sesler:
- Kelime başındaki ünsüz kümesi — araya ünlü eklemeyin: browser /ˈbɹaʊ.zəɹ/, query /ˈkwɪɹ.i/, translate /tɹænzˈleɪt/, propagation /pɹɑpəˈɡeɪʃən/, newsletter /ˈn(j)uzˌlɛtɚ/
- /æ/ — “e”den daha açık: cache /kæʃ/, backbone /ˈbækˌboʊn/, translate /tɹænzˈleɪt/, ample /ˈæm.pəl/
Bu videoyla nasıl çalışılır
- Videonun tamamını konuşmadan bir kez dinleyin ve bilmediğiniz kelimeleri not edin.
- Normal hızda cümle cümle tekrar edin; ritminiz konuşmacıyla aynı olana kadar her cümleyi yineleyin.
- Kendinizi kaydedin ve orijinaliyle karşılaştırın; cache, query, hierarchical gibi kelimelere özellikle dikkat edin.
Gölgeleme Tekniği Nedir?
Gölgeleme, başlangıçta profesyonel tercüman eğitimi için geliştirilen ve çok dilli Dr. Alexander Arguelles tarafından popüler hale getirilen, bilim destekli bir dil öğrenme tekniğidir. Yöntem basit ama güçlüdür: ana dili İngilizce olan bir sesi dinler ve hemen yüksek sesle tekrar edersiniz — konuşmacıyı 1-2 saniye gecikmeyle takip eden bir gölge gibi. Pasif dinleme veya dilbilgisi alıştırmalarının aksine, gölgeleme beyninizi ve ağız kaslarınızı gerçek konuşma kalıplarını eşzamanlı olarak işlemeye ve yeniden üretmeye zorlar. Araştırmalar, telaffuz doğruluğu, tonlama, ritim, bağlı konuşma, dinleme anlama ve konuşma akıcılığını önemli ölçüde geliştirdiğini göstermektedir — bu da onu IELTS Konuşma hazırlığı ve gerçek dünya İngilizce iletişimi için en etkili yöntemlerden biri yapar.