Current configuration of /etc/resolve.conf

[Peter Boy]

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?

Any information appreciated.

Peter

[Chris Murphy]

On Mon, Dec 6, 2021 at 6:17 PM Peter Boy  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?

[Peter Boy]

Hi,
> Am 07.12.2021 um 05:12 schrieb Chris Murphy :
>
> On Mon, Dec 6, 2021 at 6:17 PM Peter Boy  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

[Chris Murphy]

On Tue, Dec 7, 2021 at 4:09 AM Peter Boy  wrote:
> Hi,
> > Am 07.12.2021 um 05:12 schrieb Chris Murphy :
> >
> > On Mon, Dec 6, 2021 at 6:17 PM Peter Boy  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“.

Yes, this was a system wide change in the Fedora 33 cycle. It
shouldn't regress but this isn't the first time I've seen the symlink
missing. It's just that we don't have an automated test to look for
it, mainly because there's no reason to think it would just suddenly
not get created correctly mid-release.
https://fedoraproject.org/wiki/Changes/systemd-resolved

[Peter Boy]

Hi,
> Am 07.12.2021 um 10:08 schrieb Peter Boy :
>
> Hi,
> > Am 07.12.2021 um 05:12 schrieb Chris Murphy :
> >
> > On Mon, Dec 6, 2021 at 6:17 PM Peter Boy  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.
> > >
> > > …
> >
> > 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“.

Sorry, I got carried away and took the opportunity to update and expand our Fedora Server user documentation at the same time. This was more work than planned.

Anyway, the net installation also has this problem. Among other things, this has the effect that Split DNS no longer works.

@Chris: Do you know if this is being worked on? Or are we just waiting for F36?

Thanks
Peter

[Chris Murphy]

On Sat, Dec 11, 2021 at 3:03 AM Peter Boy  wrote:
> Hi,
> > Am 07.12.2021 um 10:08 schrieb Peter Boy :
> >
> > Hi,
> > > Am 07.12.2021 um 05:12 schrieb Chris Murphy :
> > >
> > > On Mon, Dec 6, 2021 at 6:17 PM Peter Boy  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.
> > > >
> > > > …
> > >
> > > 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“.
>
> Sorry, I got carried away and took the opportunity to update and expand our Fedora Server user documentation at the same time. This was more work than planned.
>
> Anyway, the net installation also has this problem. Among other things, this has the effect that Split DNS no longer works.
>
> @Chris: Do you know if this is being worked on? Or are we just waiting for F36?

We need to find out why it's not being created at installation time
only for Server. I suspect it's not just Server, but anytime Anaconda
installs RPMs to destination, rather than the typical desktop
installation, in which Anaconda uses rsync. But I don't know what's
responsible for creating the /etc/resolv.conf symlink in the two
installation methods.

cc'ing some folks who may know.