> Am 21.01.2023 um 11:19 schrieb Casper <[email protected]>: > > I usualy disable systemd-resolved on my servers, because it is not > working well... > > For disabling, I use /etc/resolv.conf file which is the main > entrypoint for administrators. > > ... > I would like systemd stop overwriting my config. In my case, servers > are not working when systemd-resolved is enabled.
Obviously my post from earlier today got lost, probably due to issues with the mailing list today. By providing your own /etc/resolv.conf you do not *disable* systemd-resolved, if it’s that what you really want to achieve. It’s just a part of it. You would have to [—]# systemctl stop systemd-resolved [—]# systemctl disable systemd-resolved [—]# rm /etc/resolv.conf [—]# vi /etc/resolv.conf <insert> domain <YOURDOMAIN>. # optional search <YOUR SEARCHPAFH> #optional nameserver <NAMESERVER_IP> nameserver <BACKUP_NAMESERVER_IP> < save&quit> In that case NetworkManager takes over to manage /etc/resolv.conf. If you don’t want this, too, you have to [—]# vi /etc/NetworkManager.conf [main] dns=none However, all of this is not advisable. Rather, my question is, what exactly doesn’t work well. We are aware of issues with libvirt virbr0 virtual network interfaces and various parts of systemd. One of them is systemd-resolved and specifically split DNS resolving. -- Peter Boy https://fedoraproject.org/wiki/User:Pboy [email protected] Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora docs team contributor Java developer and enthusiast _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
