Systemd has really gone off the rails, hasn't it? It's like they decided one day, "Hey, let's make sure no one can run their own DNS server without jumping through hoops!" Systemd-resolved squatting on port 53 is a prime example of how this system has become a control freak. You want to run your own DNS server? Tough luck! Systemd thinks it knows better, hogging the port like it's the only one allowed to handle DNS queries.

It's not just about owning the port; it's about how they've complicated what was once a simple task. You used to just configure your DNS server, point resolv.conf where you needed it, and that was that. Now, you have to delve into resolved.conf, fight with service configurations, and maybe even disable parts of systemd just to get back control over your own system.

This is not just an inconvenience; it's a design philosophy that feels like an overreach. Systemd is supposed to manage your system, not dictate how you can or cannot use your own resources. The fact that you might have to jump through all these hoops just to run a service that's been standard for decades is infuriating. It's like systemd is saying, "You want to do something simple? Here, let's make it as hard as possible."

And let's not forget the irony. Systemd was supposed to simplify things, make everything more interconnected and efficient. Instead, it's turned basic system administration into a labyrinth where even something as fundamental as DNS server setup becomes a battle against the system itself.

In short, systemd's approach to DNS handling is just another example of how it's strayed from the Unix ethos of simplicity and user control, turning system admins into problem solvers for issues that shouldn't even exist.