On 26/06/2021 10.31, Ed Greshko wrote:
On 26/06/2021 08:24, ToddAndMargo via users wrote:
On 6/25/21 5:00 PM, Ed Greshko wrote:
I don't know were that snippet comes from. But, the "Not found" may be due to dig using the system's
resolver to first get the IP of resolver1.opendns.com. So, I would have used the IP of that instead.
I would still check the nsswitch.conf files.
After a (late May update) I had problems with name resolution and tracked it down to this line on the name server host:
hosts: files myhostname resolve [!UNAVAIL=return] dns
and this fixed it for me
hosts: files myhostname resolve dns
YMMV
My computer is functioning perfect under the prior kernel.
I am not sure why you want the /etc/nsswitch.conf, but
it is anyway. Kernels should not affect it.
I try not to discount anything when I have no idea where the problem lies.
FC34 VM:
$ uname -r
5.11.16-300.fc34.x86_64
So, the nsswitch.conf files are the same. But you've not updated your VM. So, to just state
you VM's are working didn't disclose that bit.
Since you can take snapshots of VM's. Why not take a snapshot before an upgrade, then upgrade to
the latest kernel and see if you can reproduce the error?
--
Eyal Lebedinsky (fedora@xxxxxxxxxxxxxx)
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
