Kevin Fenzi wrote: [...snip loads of useful information...]
So, I think if you:
disable systemd-resolved
To that end, the change proposal¹ when systemd-resolved was enabled by default (F33) contains an example of how to ensure the service remains disabled -- which would avoid the situation Sam had where it got installed due to a dependency chain and then started because the preset enables it.
sudo bash -c 'mkdir -p /etc/systemd/system-preset && echo "disable systemd-resolved.service" >/etc/systemd/system-preset/20-systemd-resolved-disable.preset'
I used that at the time and have not had systemd-resolved start up on any updates or upgrades (so far and IIRC).
¹ https://fedoraproject.org/wiki/Changes/systemd-resolved#Fully_opting_out_of_...