Hi,
Am 07.12.2021 um 05:12 schrieb Chris Murphy
<lists(a)colorremedies.com>:
On Mon, Dec 6, 2021 at 6:17 PM Peter Boy <pboy(a)uni-bremen.de> wrote:
>
> Hi,
>
> if I remember correctly, with the switch to systemd-resolved in F33, the file
/etc/resolve.conf is no longer managed by NetworkManager. It is replaced by a link to
/run/systemd/resolve/stub-resolv.conf. On my F34 production systems this is indeed the way
it is.
>
> While updating our documentation to F35 I performed several Fedora Server test
installations with everything as default and noticed, that /etc/resolve.conf is again a
file and managed by NetworkManager. Systemd-resolved is up and running and responds to DNS
queries.
> The resolvectl command says "resolv.conf mode: foreign“ (I take it as
NetworkManager) instead of „stub“ as my F34 systems.
>
> Did I miss something? And is there a reason?
Silverblue is also affected. Workstation is not affected.
Does it make a difference is Server edition is installed using
netinstall vs dvd ISO?
Very good idea / question! I’ll check that today.
I take from your info it is a bug or at least an "unintended outcome“.
Best
Peter