How DNS Works Visually | dns | 最新泰语歌曲

How DNS Works Visually – 泰语音乐信息

在这里查看更多泰语歌曲: https://pickpeup.com/music-of-china/

See also  🔴 Sleep 24/7【100%無廣告 ,睡眠音樂】睡眠音樂 輕音樂 輕快 | 深度睡眠 | 睡眠轻音乐 放松 | 純音樂 輕快 安靜音樂 | 放鬆音樂 背景音乐 轻快 | 禪修音樂 心靈 | 音乐 | 最新泰语歌曲

dns – 与本主题相关的信息.

Visual guide on understanding how DNS (Domain Name System) works when making requests on the internet. In this video we will understand:

See also  《那年花開月正圓》CUT50 周瑩起死回生再次拒絕沈星移 少爺大怒以拳砸牆 | 那年花開月正圓49 | 最新泰语歌曲

– DNS
– Recursive resolvers
– TLD top-level domain name
– IANA root nameservers
– Authoritative nameservers

您可以在这里找到世界各地的更多乡村歌曲信息: https://pickpeup.com

See also  How to Create a Gmail Account in Bangla Tutorial | Gmail id খোলার নিয়ম | Gmail ID কিভাবে খুলতে হয় | gmail | 最新泰语歌曲

How DNS Works Visually | 与该主题相关的图像.

How DNS Works Visually
How DNS Works Visually

与主题相关的搜索 dns.

#DNS #Works #Visually.

How DNS Works Visually.

dns.

dns,domain name system,aws,cloud computing,how DNS works,dns explained simply,the simple engineer

非常感谢您观看这首歌。

26 thoughts on “How DNS Works Visually | dns | 最新泰语歌曲”

  1. Some ppl are still confused why we have many DNS servers. And so why we have so many DNS servers? Simple, to avoid single point of failure. For example, just imagine when we only have one server. What if that server failed, who's gonna back it up? Imagine if Google's own server failed, or any network just for reference. That's how and why network engineers came up with multiple servers. And basically, when you only have one server, just imagine the struggle how it will handle the load of traffic. And having multiple server architecture also grants better security.

    Reply
  2. what if the resolving query fails or root server does not know were to get the IP information..Will it ask other DNS servers to get the information and route further to TLD or AN Server

    Reply
  3. Honestly, it makes it much more clear when you put the whole thing in one pic instead of dividing it into multiple sections explaining each concept like the others…. Thanks you sir

    Reply
  4. Hey, thanks for the explanation! Clear and informative. A few improvements I would suggest to make it clearer and easier to follow:

    1. Your images work well along with the explanations you give, but I think you could take a bit more care in how they are laid out. For instance at 7:00 in the video, your diagram has become quite complicated and there are lots of lines which cross over other lines; it's tough to remember what was happening in the early stages if the lines are obscured by the later parts! Another example: at 10:20 your arrows are a bit all over the place, making it hard to tell at a glance what order the requests/responses are sent.

    2. You stumbled once or twice in your explanation, and I also noticed a lot of filler words/phrases, eg 'Essentially', or 'What's known as'. Most of the time these don't really add anything (It's not 'essentially' Google's homepage, it IS Google's homepage). Maybe you could try writing down what you're planning to say first and then reading it as a script – this will make it easier to streamline your explanations a little (and make the video shorter and clearer).

    3. Some minor graphical glitches, eg the numbers for your steps aren't centred very well in their boxes. Small details but it was a bit of a distraction for me!

    Enjoyed the video, looking forward to seeing more 🙂

    Reply
  5. very clear and informative! Thank you. I didn't know the flow went past the root name servers, them being called "root" and all haha. I wonder who manages the TLD and authoritative nameservers?

    Reply
  6. How do the domain<->IP address mappings appear on the nameserver? And how does the TLD server become aware of the authoritative nameservers?

    I've set up sites with GoDaddy before, and I know I've created something like an A record or something like that. Is goddady essentially one of the authoritative nameservers?

    Reply

Leave a Comment