Let’s implement DNS to learn history!

on YouTube ↗10m

" summary

Over 256 RFCs define DNS so the exercise focuses on specific surprises: implemented a name server from RFC 1035, finds an erratum where the TTL is documented as a signed 32‑bit when it should be unsigned and notes that error was discovered decades later, observes DNS labels accept any byte so a label can literally be "google.com" which breaks tools like Wireshark, and demonstrates the protocol quirks rather than restating the topic.

AI-written summary · about

" chapters (6)

1. 0:00DNS introduction and purpose
2. 1:40DNS RFC specifications
3. 3:04Building DNS server RFC 1035
4. 4:46DNS origins history
5. 6:34DNS security evolution
6. 8:41DNS design consequences

" related talks

• 40mScaling DNSArtem Gavrichenkov · HighLoad++ 2017
• 01h 27mDNS at 30Jim Hague · ACCU 2017
• 28mDarwin & ProtocolsPaul Mockapetris · dotScale 2013
• 15mYou Depend on DNS, This Is How It Works and You Won't...Philip Rowlands · SREcon23 Europe/Middle East/Africa
• 26mMisuse of DNS, the Second Most Used ProtocolEmilio Couto · Black Hat Asia 2020
• 20mEverything about DNS you never dared to ask!Ole Michaelis · ElixirConf EU 2022
• 52mCalloused DNS: doing it rightLev Nikolaev · РИТ++ 2017
• 16mSCALE: Automatically Finding RFC Compliance Bugs in DNS NameserversTodd Millstein, Siva Kesava Reddy Kakarla, Ryan Beckett, George Varghese · 19th USENIX Symposium on Networked Systems Design and Implementation (NSDI '22)