Author of that (terrible) article here. The blunt of this article written at (probably) 1 in the morning is something I think either I failed to mention or should have made more clear: for most of this, we just want to side-skirt the major outages of people like Cloudflare. For the few like myself, this is a breeding ground to experiment. Right now, I don't have the energy to convert services I maintain that are public to other platforms. It would mean significant downtime just to learn. However, Farer lets me play around and see what works, K8s/K3s being a prime example.

> making a mistake ... in banking on CoreDNS Well, I'll start by quoting the article: "Sanely hosting services 101 ... The first step is to not be us ... we created a lot of complexity that was generally [un]necesssary." You are 100% right in saying that BIND is more than likely a better solution than CoreDNS. And although some of it is "well, I found this that should work," it sometimes boils deeper, namely in the case of CoreDNS. It's something included in every pod of K3s and makes sense to get familiar with; which loops back to the start of wanting to learn how things work.

tl;dr : I appreciate the insights! Things are done for: a reason, for fun/experiment, or no reason. The Internet has some expected uptimes (not to say we don't for our intranet), but considering the small circle of trust, we aren't as constrained to the angry fist-waving when it goes down, rather we're all trying to figure out what happened, how to fix it, and how to prevent it from being an issue again: a fun "practicum," per se.