I thought that having the network subsystem manage resolv.conf dynamically had been pretty standard since well before systemd came along. e.g. Most DHCP client

I thought that having the network subsystem manage resolv.conf dynamically had been pretty standard since well before systemd came along. e.g. Most DHCP clients have done that since... well, probably since DHCP was invented. See, for example: https://wiki.debian.org/resolv.conf https://wiki.debian.org/resolv.conf If you want a static resolv.conf, but you're not using a completely static network config and have some kind of dynamic network management daemon, be that `dhclient`, or `NetworkManager`, or `systemd-resolved`, you've always needed to explicitly configure it to leave resolv.conf alone. Not sure how this is a systemd issue?