4 ms·
>Why the fuck is my init system doing DNS resolution? SystemD is more than just an init system, it also runs some system service, like DNS. If you still think
by jeroenhd 6y ago
>Why the fuck is my init system doing DNS resolution?
SystemD is more than just an init system, it also runs some system service, like DNS. If you still think of systemd as an init system, then your knowledge of it is outdated by at least a couple of years.
But, if you want to use it as merely an init system, feel free to disable resolved and install dnsmasq instead like in the Good Old Days.
I'd much rather have my system not working than have it randomly start sending the domain part of my browser history to Google without as much as a notification. When you install Fedora, the last thing I'd expect is that it starts acting like a tracker for Google when my DNS server goes down.
I think they should've implemented this differently, sending out a notification that the DNS configuration is broken, with the option of switching to either Google, Cloudflare or letting me fix the network configuration instead of silently failing.
The less tech savvy users are still running Windows where the exact same thing would've happened, with errors just as obscure. No matter what OS you're running, the problem is with your network config, so it should be fixed by whoever manages that instead of relying on some hard-coded defaults somewhere deep inside the DNS resolver. In most cases, that means calling your ISP or calling your IT service desk for support.
I personally hate it when software goes and does some random shit like pick its own DNS server because it somehow has determined that something was broken. Windows is full of this "smart" behaviour and it's one of the reasons I always feel like I need to anticipate its responses to my actions instead of just using it.
- jcelerier 6y ago> . If you still think of systemd as an init system, then your knowledge of it is outdated by at least a couple of years. a couple years ? here's the blog post from 2011, a decade ago: http://0pointer.de/blog/projects/why.html http://0pointer.de/blog/projects/why.html There's been as much time between now and this blog post, than there has been between this blog post and the introduction of windows fucking XP ! > systemd is in the process of becoming a comprehensive, integrated and modular platform providing everything needed to bootstrap and maintain an operating system's userspace. It includes C rewrites of all basic early boot init scripts that are shipped with the various distributions. > systemd is also a big opportunity for Linux standardization. Since it standardizes many interfaces of the system that previously have been differing on every distribution, on every implementation, adopting it helps to work against the balkanization of the Linux interfaces. Choosing systemd means redefining more closely what the Linux platform is about. This improves the lifes of programmers, users and administrators alike. being more than an init system has been the goal of the project since pretty much the beginning
- ryandrake 6y agoI’m waiting for the day systemd includes a chat and e-mail client. Maybe a built-in version of emacs and a spreadsheet application too.
- benttoothpaste 6y agoI can probably live with systemd-emacsd, but once we reach the stage of systemd-electrond, I’ll definitely retire for good.
- marcosdumay 6y agoWhile they are at it, we could use some new take on Bash too, Dash doesn't break enough scripts to fill HN threads. And some new find, cp and ls with mostly the same options, but some having the same names of the GNU ones but that overwrite data at random. And I'm eager to discover what the systemd folks can do in a remake of tar!
- jeroenhd 6y agoI was trying to be conservative because I've only really dealt with systemd since about 2016, but damn, nearly a decade of systemd and people still fight systemd vs systemV like it's 2011. I'm not against systemd myself, to be clear. I think putting services like these into modules of the systemd environment makes sense, and as long as you can disable them if you don't want them, that's perfectly fine. I've had to disable one of them on one of my servers because _something_ was going wrong preventing resolved from caching repeated DNS responses, causing a huge load when a script started scraping a particular domain without any clear indication as to why in the logs. As long as I can do that, I'm perfectly fine with whatever the systemd folks want to integrate next!