> DNS broke my site for three hours. But now I actually understand it I have been broken for three decades and I still don't understand DNS. It is a simple protocol but people use it in complicated manners.
why you need DNS for at server? just use hosts file. why your server would need to resolve domains on the internet? client yeah, server no.
You have to go back five decades if you want to use a host file. My point is that cache and making are the three hard things in computer science DNS has had both problems several times. I choose DNS over hosts files every time.
> DNS broke my site for three hours. But now I actually understand it I have been broken for three decades and I still don't understand DNS. It is a simple protocol but people use it in complicated manners.
Simple? Oh no. Simple it is not. It's the most baroque protocol that is still somehow surviving from the initial Internet. There are so many weird limitations, like not being able to use CNAME for apex zones. Or the entire DNSSEC fiasco.
I think CNAMES were a mistake, think of them as lightweight NS records. It is a simple protocol solving a rather complex system. I have respect for simple things I have tried implementing my own server, did not go well.
Cool, but the macOS commands being wrong irks me. You could at least check them before publishing. It seems like you used an LLM to write that part. And the table "quick reference" at the end is also a LLM tell.
and the formatting, and "the cool part? the weird part? the catch?", and "engaging" questions at the end of not just this but other posts on that blog
unfortunately the writing is getting praised even here so it will continue
Well written. Shared with less technical colleagues. DNS witchcraft is never really understood — having a clearly written, understandable article is extremely useful.