Hi Michael,
Could you please provide more details? This is content of my nsswitch.conf:
~~~
$ grep mdns4_minimal /etc/authselect/user-nsswitch.conf
hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
~~~
How that happened? From what version of what package it happened? Why
should I do some changes manually and they are not handled automatically?
Thx
Vít
Dne 09. 09. 20 v 21:08 Michael Catanzaro napsal(a):
Hi,
I've you've installed or upgraded to Fedora 33 (or to rawhide) prior
to today, your /etc/nsswitch and /etc/resolv.conf are probably in a
broken state that requires manual intervention to resolve. This has
caused breakage for mDNS and VPN users [1][2][3]. Apologies for this
breakage. Anyone installing with current nightly images or upgrading
as of today should be OK, so users installing F33 beta or upgrading
from F32 to F33 beta will be unaffected.
To fix /etc/nsswitch.conf, edit the hosts line in
/etc/authselect/user-nsswitch.conf to look like this:
hosts: files mdns4_minimal [NOTFOUND=return] resolve
[!UNAVAIL=return] myhostname dns
Then run:
# authselect apply-changes
Then, fix /etc/resolv.conf:
# rm /etc/resolv.conf
# ln -s ../run/systemd/resolve/stub-resolv.conf
And restart NetworkManager:
# systemctl restart NetworkManager.service
Michael
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1873856
[2]
https://bugzilla.redhat.com/show_bug.cgi?id=1867830
[3]
https://bugzilla.redhat.com/show_bug.cgi?id=1863041
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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