Anthony F McInerney writes:
Note that the selected mode of operation for this file is
detected
fully automatically, depending on whether /etc/resolv.conf is a symlink to
/run/systemd/resolve/resolv.conf or lists 127.0.0.53 as DNS server.
Again: why does anything have to be "detected fully automatically"?
We've had a mechanism for controlling symlinks for an eternity:
alternatives.
I cannot see any valid technical argument against having /etc/resolv.conf
managed by alternatives. If systemd-resolved wishes to have the highest
alternatives priority, and thus ends up being the resolver by default,
that's fine.
Does anyone have an argument /against/ having /etc/resolv.conf managed via
alternatives? What can't you do with alternatives that you can with the
current ham-fisted approach, where someone has to go out of their way to
figure out how to switch to network manager-provided resolv.conf?