All language subtitles for 4. TLD Servers

af Afrikaans
sq Albanian
am Amharic
ar Arabic Download
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bn Bengali
bs Bosnian
bg Bulgarian
ca Catalan
ceb Cebuano
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
tl Filipino
fi Finnish
fr French
fy Frisian
gl Galician
ka Georgian
de German
el Greek
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
km Khmer
ko Korean
ku Kurdish (Kurmanji)
ky Kyrgyz
lo Lao
la Latin
lv Latvian
lt Lithuanian
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mn Mongolian
my Myanmar (Burmese)
ne Nepali
no Norwegian
ps Pashto
fa Persian
pl Polish
pt Portuguese
pa Punjabi
ro Romanian
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
st Sesotho
sn Shona
sd Sindhi
si Sinhala
sk Slovak
sl Slovenian
so Somali
es Spanish
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
te Telugu
th Thai
tr Turkish
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
or Odia (Oriya)
rw Kinyarwanda
tk Turkmen
tt Tatar
ug Uyghur
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:04,960 --> 00:00:10,870 Hi, guys, and welcome back picking up from where we left off our next stop down the road of having 2 00:00:10,870 --> 00:00:13,930 a query resolved is top level domain name service. 3 00:00:14,960 --> 00:00:19,040 We have already seen that in follow the route in the syntax of a domain name. 4 00:00:19,340 --> 00:00:25,280 And in the district in this lecture, we will see that they do so in the process of name resolution 5 00:00:25,280 --> 00:00:25,550 to. 6 00:00:26,910 --> 00:00:32,010 Following up from our previous discussion on the journey of a DNS request, thanks to the root servers 7 00:00:32,010 --> 00:00:38,520 referral, it is now up to the referred TLT name server to take on the mantle of name resolution and 8 00:00:38,520 --> 00:00:41,790 take us one step closer to having a query resolved. 9 00:00:42,850 --> 00:00:48,730 The responsibility of the till the nameserver is simply to provide a referral of its own that will contain 10 00:00:48,730 --> 00:00:52,210 a server authoritative for the domain we want to browse to. 11 00:00:52,690 --> 00:00:53,800 In this case, Yahoo. 12 00:00:55,190 --> 00:00:58,370 At this point, you might wonder why all this back and forth communication. 13 00:00:59,430 --> 00:01:05,460 If you remember from a previous lecture, DNS uses a hierarchical name architecture with a globally 14 00:01:05,460 --> 00:01:11,010 distributed system of databases instead of using a flat name architecture featuring a single database 15 00:01:11,010 --> 00:01:14,760 of information with authority of all domain names and that data. 16 00:01:15,930 --> 00:01:22,410 Instead, due to the protocols, hierarchical nature, each branch of the tree offers the information 17 00:01:22,410 --> 00:01:29,040 it has, the root server doesn't know the server hosting WW Dot Yahoo.com. 18 00:01:29,490 --> 00:01:34,650 But it does know about the code name servers, which is why it previously provided a referral for one. 19 00:01:35,680 --> 00:01:43,270 In the same manner they're referred to as the nameserver doesn't know about the system hosting www.youtube.com 20 00:01:43,270 --> 00:01:43,780 either. 21 00:01:44,170 --> 00:01:49,390 But it does know about the name server responsible for the Yahoo part of the domain to which it is now 22 00:01:49,390 --> 00:01:51,550 passing the bucket via its own referral. 23 00:01:52,950 --> 00:01:58,470 In other words, each level of the hierarchy provides a piece of the puzzle needed for the requested 24 00:01:58,470 --> 00:01:59,880 domain name to be resolved. 25 00:02:00,870 --> 00:02:07,110 By now, it's probably become clear that most operational aspects of the NSA hierarchical from the way 26 00:02:07,110 --> 00:02:12,690 domain names are formatted and structured in the downstream, down to the way they are translated when 27 00:02:12,690 --> 00:02:13,140 browsing. 28 00:02:14,930 --> 00:02:21,440 So in summary, the main job of the till the nameserver is to pass back a referral with a name server 29 00:02:21,740 --> 00:02:24,140 that has authority over the requested domain. 30 00:02:24,530 --> 00:02:25,520 Yahoo in this case. 31 00:02:27,110 --> 00:02:32,990 There are several categories of till days of which the most important ones to know are generic top level 32 00:02:32,990 --> 00:02:40,150 domains abbreviated as list and country code, top level domains abbreviated as CC till date. 33 00:02:41,520 --> 00:02:46,950 Generic top level domains are supposed to reflect the type of industry or space that the organization 34 00:02:47,400 --> 00:02:49,590 in ownership of that domain falls into. 35 00:02:50,340 --> 00:02:56,250 For example, it is standard practice for governmental agencies to use the Golf GTI Elite, such as 36 00:02:56,550 --> 00:03:09,440 the U.S. Golf and for universities to use the EDU- as a University of Oregon does at WW Dot You Oregon 37 00:03:09,480 --> 00:03:10,440 Dot Edu. 38 00:03:12,480 --> 00:03:14,900 The original gTLD days were ARPA. 39 00:03:15,000 --> 00:03:24,570 Com A Aidoo of M. Met and Oak, but the lease has grown bigger with additional fields such as Aero and 40 00:03:24,810 --> 00:03:27,840 Pro Info and many others joining the group. 41 00:03:29,160 --> 00:03:35,220 Country code top level domains have been created to allow countries to manage their own namespace and 42 00:03:35,220 --> 00:03:40,350 make it easier for their citizens to find the resources they need in the languages they understand. 43 00:03:41,520 --> 00:03:48,510 Greece, Italy, for example, East Asia, Japan's country code, top level domain is cheap and Poland 44 00:03:48,510 --> 00:03:49,460 is pope. 45 00:03:50,880 --> 00:03:57,660 Interestingly, countries can also use organizational subdomains within the country code top level domains 46 00:03:58,470 --> 00:04:06,330 UK, for instance, uses the UK for companies operating in the country, while Australia uses dot com 47 00:04:06,330 --> 00:04:08,700 dot a--you for its own corporations. 48 00:04:10,160 --> 00:04:18,290 Other categories of top level domains are still these identical days and utilities since they fall outside 49 00:04:18,290 --> 00:04:20,690 the mainstream of top level domains. 50 00:04:20,720 --> 00:04:25,310 We will not go over them in this course, but you are more than welcome to research them in your own 51 00:04:25,310 --> 00:04:25,640 time. 52 00:04:26,030 --> 00:04:33,530 The full list of top level domains can be found at HTTPS Kollan Forward Slash Forward Slash W, WW Dot 53 00:04:33,680 --> 00:04:40,400 I-A and a dot org forward slash domains forward slash route forward slash DB. 54 00:04:42,080 --> 00:04:47,630 So now with the till the name service assistance, we will proceed to the next lecture to continue our 55 00:04:47,630 --> 00:04:52,370 journey down the dentistry by contacting the preferred authoritative names of. 56 00:04:53,350 --> 00:04:55,510 Thank you for watching, guys, and I will see you in the next one. 6236

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.