On 2/16/21 6:05 AM, David Both wrote: > This situation is due to the change from the old resolver to the new systemd-resolved. > > I have a page on my technical web site that describes the problem and the circumvention. > > http://www.linux-databook.info/?page_id=5951 > > This does not, erm, resolve the problem but it does get you back to a working resover. Right stopping/disabling the systemd-resolved then creating your own /etc/resovled.conf is the work around... systemd is in the booting business... However did it get in DNS business... And that was a good idea??? ;-) > > I hope this helps. It did... Thanks you! steved _______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
