Alright, buckle up because here comes a rant about systemd, the bane of Unix purists and the headache of system administrators everywhere:

Fuck systemd, seriously. It’s like the developers took the Unix philosophy, balled it up, and tossed it out the window. What was once a beautifully simple, modular system has been hijacked by this monstrosity of an init system that thinks it needs to control every goddamn aspect of your Linux box.

Remember the days when you could just tail your logs to see what's going on? Now, you've got to fumble around with journalctl like you're trying to solve a fucking Rubik's Cube. Binary logs? Who the hell thought that was a good idea? It’s like they wanted to make debugging as painful as possible. "Oh, you want to see what went wrong? Here, decrypt this mess with some arcane command!"

And don't even get me started on the boot process. Systemd decided to shove its nose into every nook and cranny, turning what used to be a straightforward, albeit linear, boot sequence into a goddamn spider web of dependencies and services. If one thing's off, your whole system might as well be down because good luck figuring out which of the hundred little unit files fucked up.

Complexity for the sake of complexity, that's what systemd is. It's like they took the KISS principle and turned it into "Keep It Superfucking Complicated." Every little thing now needs a systemd unit file, making what used to be simple scripts into a convoluted mess. And if you dare to deviate from the systemd script? Prepare for a cascade of errors that could bring down your system faster than you can say "I miss SysVinit."

The resource management? Oh, please. Mounting /tmp as tmpfs just to avoid using rm -rf? That's not innovation; it's memory waste. It's like they've never heard of the concept of efficiency. Why bother with RAM when we could just keep things straightforward and disk-based?

And let's not forget the arrogance. Systemd isn't just an init system; it wants to be your network manager, your logging system, your cron replacement. It's like a power-hungry dictator in the Linux world, absorbing everything into its bloated self, leaving no room for alternatives or simplicity.

To all the systemd developers: You've taken something beautiful, something universally loved for its simplicity, modularity, and elegance, and turned it into a sprawling, incomprehensible behemoth. You've made Linux administration not just a job but a fucking puzzle where the pieces keep changing shape.

In conclusion, systemd is an affront to the Unix spirit, a nightmare for those who cherish simplicity, and a daily reminder that sometimes, innovation means making things unnecessarily complicated. Here's to hoping for the day when we can uninstall this mess and go back to systems that don't require a PhD in systemd-ology just to reboot your machine.

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.