Комментарии:
ICAN: we are non profit organization
But but but we charge you huge money 💰
YOU ALWAYS TALK TO THE POINT. AMAZING AND TIME SAVING
ОтветитьGenuine question. Why do we need 3 servers for it?
Ответитьso much info in 100s.
Ответитьbetter than explaination than the shitty guy at bits and byte of networking course.
ОтветитьGreat video for people who have previously learned computer networking but need a refresher on certain parts.
ОтветитьSorry i got confused when It comes to DNS! I cant understand 😭😭
ОтветитьMost requests aren’t recursive!
ОтветитьI have learnt a lot of new things that I have never worked with from your videos, like AWS, nginx, kubernetes, graphQL(and other dbs), typescript to name a few. One thing that I don't understand is how they work together. I would really love to see a video where you design a mock system using all of these (and possibly more) and explain each of their roles and why you chose it (kinda like your reverse-cloud migration video using raspberry pi).
Whenever I think of a software architecture I think of them as several layers that interact with each other. However, I am unable to assign which layer what belongs to by watching a stand alone tutorial about a single tool.
Btw, I am a college senior pursuing CS major and I love your content. Thanks for all the awesome contents.
Additionally the TXT records are used for email security (SPF, DKIM, DMARC records).
ОтветитьNow, to answer the "What happens when you enter a URL into a web browser" interview question with this and see them stop me before getting to the TCP handshake part.
ОтветитьPowerful 100 second
ОтветитьFun thing is the recursive resolver is an iterative resolver.. it does queries one server after another on its own. It’s just that it gets the addresses from previous calls
Ответить+! for dnsec
ОтветитьOne over DHCP
Ответитьmore of this, a little longer and slower, network system/ programming/ computer science
ОтветитьIs this a reupload?
ОтветитьPlease do PKI
ОтветитьIt was only a matter of time before the fireship:// protocol resolved DNS.
ОтветитьCan you do CS degree in 100 seconds?
ОтветитьCan’t even get the initialism correct.
ОтветитьThis video looks like slowed down compared to other videos.
ОтветитьSuperb
ОтветитьI'm kinda demotivated to learn further after the release of GitHub Co-pilot
ОтветитьI think you have just explained, the first semester of my course in 100 secs.
ОтветитьAmazing video! Well explained!
What is FTP and how it works?
Nice! Now I need it for Proxies and Reverse Proxies 🙏
ОтветитьOne thing I've learned from this channel, if not everything, is that I can do anything.
Ответитьbut thats 135 second --_--
ОтветитьSo if A stands for Address that must mean AAAA is for AAAAddress
ОтветитьThe A record and NS look the same though
ОтветитьFuture video: Computer Science in 100 seconds
Ответить100 sec on Kotlin please :)
ОтветитьЛол, я думал, тут про магазин ДНС
ОтветитьIts not a recursive resolver, its a hybrid resolver.
Ответитьthe "s" sound throughout each video kind of annoying
ОтветитьFireship just knows when you need something.
Also, please please demystify this DNS thingy further.
Always High Quality Videos Fireship... Thanks. Commenting so the algorithm blesses you sir
Ответитьfinally a fireship video where I already knew what he was explaining 😅
ОтветитьI like you tone.
ОтветитьHey Jeff, thnx for the awesome videos!
A "100 seconds of event-loop" video would be very cool 😎
I have an exam today !
I know how DNS works
And I still want to watch this
Gen Z would be like "What is a phonebook?"
ОтветитьA=“Alias” not address, right?
ОтветитьT'was a great refresher. Thank you.
ОтветитьBest 100s of my life.
Ответить