Everything You Need to Know About DNS: Crash Course System Design #4
ฝัง
- เผยแพร่เมื่อ 13 มี.ค. 2023
- Get a Free System Design PDF with 158 pages by subscribing to our weekly newsletter.: blog.bytebytego.com
Animation tools: Adobe Illustrator and After Effects.
Checkout our bestselling System Design Interview books:
Volume 1: amzn.to/3Ou7gkd
Volume 2: amzn.to/3HqGozy
The digital version of System Design Interview books: bit.ly/3mlDSk9
ABOUT US:
Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.
I literally got tears of joy by the end of the video. Do you know why? my brain realised it had a quality learning for 5:44 minutes. Hard to imagine the efforts behind making such a wonderful session.
This is the best explanation on DNS I have seen. Thank you for such a presentation.
Didn't know that you could shorten TTL before changing DNS records to ease the transition.
Very valuable information, thank you!
it will be applied for future updates, not for first update, because middle servers will still wait till their old TTL expire.
Your skill for simplify things is not from this world. Thank you, I see you! 🙏
I have seen your works from the beginning, I appreciate your hard work, thank you for making this to be more understandable.
DNS translate domain names to IP addresses. It's hierarchical and de-centralized.
This is one of the best explanations of how DNS works I have seen in a while. Thanks so much 😊🙏
check computerphile channel
Excellent video on how DNS works. Great job!
Great video, I appreciate the free content and I'm looking forward for more!
thank you for your fantastic video! the audio and video information together was superb. thank you so much and i will highly recommend this video to others
Great! You should also cover different dns record types like a record, mx record, cname, Alias etc
Amazing 👏 Short enough to keep my attention and low level enough to be interesting and informative
the editing on this video is top notch.. thanks!
Awesome explanation!!
Awesome illustrations, keep it up 👍🏿
Very nice!
Thank you for your efforts.
best channel on system design
I love this channel!
Thanks for the Info, man
What A Great Explanation, Wow
Perfect! Thank you!
Love your channel
Thanks for sharing.
May i ask which tool you have used to make this animation, It's very impressive.
Thank you for explaining in a nutshell
Really enjoy your youtube articles. Would you cover the difference between recursive and iterative dns query may be on another youtube episode. Thank you!
Great video!
this was a fire explanation....🔥🔥🔥🔥🔥
Very well explained
Amazing videos! What library/tool are you using to make the videos? Pleeease, share.
Great video, very informative
4 quick questions....
1. Who owns the ip address of DNS resolver
2. Browser sends http request which is stateless, so every time it will go to check the dns resolver
3. How browser solves this quickly can you elaborate this much more.
4. Who will update the ip addresses of TLD name servers
BBG never disappoints!
Fantastic!!!
Amazing info, thanks. My concern is, there are a lot of request only for translate the domain to a ip address and after of that, the browser will can get the resources for that ip address. I know that there is running in a fraction of seconds, but is there a better way today instead to add in more dns server around the world? Regards.
Great video. What did you use to create the animation? Thank you in advance.
awesome!
amazing!
I am surprised that there was no mention of ICANN in the video. Where does ICANN stand in the DNS resolution? Are you referring to ICANN as Root resolver here?
you make great videos
What is the sotware that you use for editing the videos and how are you gathering different images and flowcharts of design?
Missed a few catches: browser(mentioned) --> OS --> router --> then ISP and so on.
Otherwise this was a fantastic explanation and I always love your animations!
What software or tool do you use for the animations?
I love the way you explain things you think you can do a playlist on dynamic programming ? Related to getting a job on an approach to solve leetcode or hackerank questions I think it may help us uk people apply for jobs thanks again!
Will we be able to capture the redirects happening between resolver, root, TLD servers in our browser developer tools network tab??
can you do iptables next?
Very nice video but can u tell me where dns resolver and dns server will be located???
Can you explain DNSSEC too?
Can you explain DNS in email role. I can't under it
I have a quick question. What is the logic to identify the country from the IP address.
I don't understand how does an operating system participate in domain name resolution except for providing "open()" and "socket()" system calls to open files and do network communication using sockets?
can someone help me: does dns resolver run on my laptop or on a server?
Why would a network be connected to a FC00 dns server and not have a number instead
You did not explain what exactly TTL is. Is it TTL of a DNS record, of a DNS cache entry, of a DNS request, of a DNS propagation event, ... ?
Is it possible to modify the DNS records in local cache of system.
It's much easier to just add records to your hosts file, which your OS checks first before resolving a name over DNS. It's in /etc/hosts on Linux/Mac, and c:\windows\system32\drivers\etc\hosts on Windows. You'll need admin privs to edit it, though.
If DNS uses UDP as the transport protocol, how does the DNS resolver correlate a given UDP request for a DNS query to any of the downstream servers to a given response? My understanding is UDP doesn’t have responses like TCP, so how do you get this “request/response” behavior?
You're mistaking the transport protocol to the application protocol. It doesn't matter if you exchange information via TCP or UDP, it only matters that TCP guarantees message delivery by using SYN/ACK messages, variable window sizes, etc.
For the application, like DNS queries, you would still get the response via UDP, but you don't waste network round-trips doing TCP.
edit. From the program perspective, the easiest implementation (and the only one on Windows, if I recall correctly) is to block the thread and wait for the UDP response. The operating systems (be it Linux, Windows or even a router) are smart enough to send the message from a specific socket to the right application thread. So your naive blocking DNS resolver will be resumed and can process further.
why do not you intruduce the dnssec
Irfan ali
1st view
I'll just stick to /etc/hosts - an OG DNS
hard to understand this diction, though. sorry to say! cause the content is ok.
A valuable content, can you explain CIDR as the similiar method?
The best