On 6/26/21 10:19 AM, James Szinger wrote:
On Fri, 25 Jun 2021 17:33:04 -0400
Tom Horsley <horsley1...@gmail.com> wrote:
On Fri, 25 Jun 2021 14:20:30 -0700
ToddAndMargo via users wrote:
Kernel 5.12.12-300 breaks host resolution
https://bugzilla.redhat.com/show_bug.cgi?id=1976371
Very weird that the kernel could break name resolution since that
all works at library level. Maybe some "deprecated" interface
is being used by 99% of the lookup code, and they got rid of
it completely in the new kernel?
I had name resolution break on one of my F34 computers after the latest
kernel update. Restarting systemd-resolved fixed the problem. I
rebooted and the same thing happened: no DNS until systemd-resolved
was restarted.
None of systemctl status, dmesg, or journalclt showed anything
suspicious or interesting.
My other Fedora computers are fine. I suspect the difference is that
the problem computer is using bridged networking instead of a direct
ethernet connection. Perhaps a timing issue with the bridge?
Jim
Hi Jim,
My only computer with the issue is also using bridge
networking.
Eyal recommendation to alter nsswitch.conf
# hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve
[!UNAVAIL=return] dns
hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve dns
worked for me.
-T
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
