Thanks Bettina I really appreciate the feedback. Feel free to share these videos around - they’re my way of giving back so I want them in front of all the people ;)
I have watched several videos about DNSSEC but nothing gave crystal clear explanations as this one. I like the graphics used as well. Thank you very much for your effort! 💚
(I know it's late, but in case if anyone's wondering) The short answer is that DNS messages are sent through UDP, which is a stateless protocol and the source IP-address is blindly trusted. So if a bad guy has an access to a query traffic, he can spam fake UDP responses pretending to be the authoritative server. It's called DNS cache poisoning, though it is difficult to implement but it's possible.
This channel is a gem and I hate youtube algorithm for delaying me finding this.
thanks :) help me spread the word.
I’ve been following these videos for 3 days and this is the easiest I’ve learned in 10 years as a tech engineer and I work for Microsoft
Thanks Bettina I really appreciate the feedback. Feel free to share these videos around - they’re my way of giving back so I want them in front of all the people ;)
I have watched several videos about DNSSEC but nothing gave crystal clear explanations as this one. I like the graphics used as well.
Thank you very much for your effort! 💚
I think youtube fixed their algorithm this summer, because now I'm starting to find jewel channels like this. Awesome stuff
Please share it around on social media. It really helps.
Clearly the best tutorial on the cloud. Very well structured and explained. Give this m’en the Oscar
Thank You for your videos .
Thanks for clear explanation! And graphics are very helpful
Glad it was helpful!
thank you
You're welcome
I love bullet points.I wish you will start to love this also.
lol... they have their place :)
#gov 1billion debt for etsi-iso, internal affair by google, inc permissive law.
why does DNS resolver easily except the result from the person who is not pointed by the root sever? at 6:00
(I know it's late, but in case if anyone's wondering) The short answer is that DNS messages are sent through UDP, which is a stateless protocol and the source IP-address is blindly trusted. So if a bad guy has an access to a query traffic, he can spam fake UDP responses pretending to be the authoritative server.
It's called DNS cache poisoning, though it is difficult to implement but it's possible.