On Wed, Sep 30, 2020 at 11:50:00AM -0500, Michael Catanzaro wrote: > On Wed, Sep 30, 2020 at 6:43 pm, Dominik 'Rathann' Mierzejewski > <domi...@greysector.net> 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
After the latest updates, this should not necessary (though it will still work). Instead, specify a preset (before the upgrade): sudo bash -c 'mkdir -p /etc/systemd/system-preset && echo "disable systemd-resolved.service" >/etc/systemd/system-preset/20-systemd-resolved-disable.preset' This is also described in https://fedoraproject.org/wiki/Changes/systemd-resolved#Fully_opting_out_of_systemd-resolved_use Zbyszek _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
