Thank you for that! It did take an hour+ to research it and write it up. And it’s kindof depressing that there’s been no movement, but I do understand that I’m not really able to contribute anything on the development side.
What you're dealing with fits in the crux of my problem with systemd. They've made a series of assumptions about how things will be on a system, and if that doesn't match your reality, well terribly sorry, adjust your reality, even if it's not possible, or realistic.
Unfortunately, unlike before, you can't easily just cut systemd out of the mix.
I'd hate it less if it were more modular, such that I could swap out distinct pieces when and if needed.
I don't even understand the rationale for some of the integration. Like systemd-resolve. Why did it need to suck in the resolver? Now I can't edit resolv.conf because it overwrites it.
I can't even find a reasonable list of everything it does. Init, mounts, login, pluggable hardware, nspawn containers, logging, and...whatever else I'm forgetting.
systemd-resolvd is, like many of the systemd components, optional.
If you're using it, it is either because you setup it yourself or your distro set up it to you or you're using a NetworkManager with systemd-resolvd as your DNS resolver (and even them, it is configurable and not the default at all).
