Have you noticed that when the blame #DNS meme starts flying the root is perfectly operational, there is rarely a mention of the big registry operators, BIND, Unbound, Knot, and PowerDNS are absent the conversation, and many who can craft a reasonable dig query are getting responses from local and public resolvers to debug?

Even with all the misconfiguration, added complexity on top of it, and burden of being used by practically every service on the Internet, we should marvel at how amazingly good the vast majority of the DNS performs despite our best efforts to overwhelm it with all the Internet junk we've created.

Here is another way to think about this phenomenon. Where are all the DNSv2 or redesign proposals? Or what IETF I-Ds are addressing the root of all problems that is this DNS problem?

What is the problem exactly?

Memes, while amusing and cute lack nuance. They are generally not very good at explaining much.

And if your solution is ENS, I will ask all my followers and beyond to point and laugh. :-)

@jtk it wasn't DNS ..it was diwali
ISC.org (@[email protected])

Honestly you all are simply *LUCKY* that the internet works at all. If/when it works, it is because people who care are working, mostly un-noticed, in the background. I am not talking only of my own colleagues.....

Fosstodon

@jtk "It's always misunderstanding DNS".
See also: "Why eventually consistent databases are misunderstood."

See also: the pending release of the 2nd edition of the helpful Networking For System Administrators by @mwl https://www.tiltedwindmillpress.com/product/networking-for-systems-administrators/

Networking for Systems Administrators

Stop waiting for the network team! If basic TCP/IP was hard, network administrators couldn’t do it. Servers give sysadmins a incredible visibility into the network—once they know how to unlock it. Most sysadmins don’t need to understand window scaling, or the differences between IPv4 and IPv6

Tilted Windmill Press