Michael Catanzaro wrote: > On Wed, Sep 30, 2020 at 6:43 pm, Dominik 'Rathann' Mierzejewski > <dominik@xxxxxxxxxxxxxx> wrote: > > What if I'm using NetworkManager and dnssec-trigger? This has been > > working very well for me for the last couple of releases and I'd hate > > to be forced to manually reconfigure things so that it starts working > > again. > > The upgrade process is designed to do the right thing for users who > stick with our defaults. Manual intervention is required for unusual > cases like this. You'll need to manually disable systemd-resolved after > upgrade, restore /etc/resolv.conf from the backup file that will be > created during upgrade, and restart NetworkManager. That would look > something like: > > # systemctl disable systemd-resolved.service > # systmectl stop systemd-resolved.service > # mv /etc/resolv.conf.orig-with-nm /etc/resolv.conf > # systemctl restart NetworkManager.service So there's no need to revert any changes to /etc/nsswitch.conf? I've seen some discussion about that file in relation to systemd-resolved. It seemed far from easy to understand how to make it work correctly. Björn Persson
Attachment:
pgpildBfOODu7.pgp
Description: OpenPGP digital signatur
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
