On Sun, 2022-04-24 at 10:48 -0700, Kevin Fenzi wrote:
> The scriptlets will set /etc/resolv.conf to point to the
> systemd-resolved resolver if: 
> 
> * The /etc/resolv.conf file doesn't exist yet
> AND
> * systemd is being used to boot (so, it's not a container, etc)
> AND
> * systemd-resolved service is enabled
> AND
> * DNSStubListener is not set to no/false/off in systemd/resolved.conf
> 
> So, if you wish to have systemd-resolved not manage your dns, you
> can: 
> * make a /etc/resolv.conf file and put whatever you want in it. 
> * disable the systemd-resolved service
> * Set DNSStubListener to no/false/off in systemd/resolved.conf

It seems to me that original complaints were that it didn't follow that
set of rules.  They had a resolv.conf file that it kept interfering
with.

I'd well imagine that initial boot up, you don't have one.  At your
first boot it may be about to be configure by DHCP, does it wait until
after that before taking over?  You may be going to manually configure
your network, do your after-the-fact configurations get acknowledged as
the settings that will be kept and not interfered with?

-- 
 
uname -rsvp
Linux 3.10.0-1160.62.1.el7.x86_64 #1 SMP Tue Apr 5 16:57:59 UTC 2022 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to