Why is DNS still hard to learn?

• dog

  2 5,535 0.0 Rust

  A command-line DNS client.

  > As a user of the "--color" flag for the `ip` command, I'd love to see tools like dig produce more modern output

  https://github.com/ogham/dog is pretty good in that regard

• tldr

  65 46,474 9.6 Markdown

  📚 Collaborative cheatsheets for console commands

  

  TIL that `dig` does not have TLDR page https://github.com/tldr-pages/tldr

• Onboard AI

  getonboard.dev

  sponsored

  Learn any GitHub repo in 59 seconds. Onboard AI learns any GitHub repo in minutes and lets you chat with it to locate functionality, understand different parts, and generate new code. Use it for free at www.getonboard.dev.

  

• dns-weekend

  3 158 10.0 Jupyter Notebook

  Code for Implement DNS in a Weekend

  I don't usually reply to HN comments, but I want to take a minute to address this one. It took me many years to feel totally comfortable debugging DNS problems, and I wrote this post to explain why I think it was hard for me.

  I also used to think that "no, actually, it's easy!" was an encouraging response to "this is hard to learn". And I kind of get it! I love DNS! I think it is surprisingly simple in many ways, and I've written about that a lot, for example in https://implement-dns.wizardzines.com which shows you how to implement a DNS resolver from scratch in some pretty simple Python code.

  But over the years I've learned that "no, it's easy to learn!", instead of coming off as an encouraging comment ("you can do it!"), often gets received as "no, it's not hard, actually the problem is that you're dumb". Like, I've been confused about this for years, and you're telling me that, no, actually it's easy? Not that helpful!

  So I've stopped telling people that, and instead I put a huge amount of work into trying to understand _why_ people find certain things hard and work to help remove some of those barriers.

Suggest a related project