On 6/25/21 3:33 PM, Ed Greshko wrote:
> On 26/06/2021 06:23, ToddAndMargo via users wrote:
>> On 6/25/21 2:45 PM, Ed Greshko wrote:
>>> On 26/06/2021 05:33, Tom Horsley 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?
>>>
>>> What I find equally weird is that in the BZ he states that his qemu VM's
are working just fine.
>>> If the VM's are working and they have been updated to the same kernel
then what would
>>> be the difference? A proxy setting perhaps?
>>
>> More funny! The VM's are using my caching name server
>> ON MY HOST !!!!
>>
>
> Sure, that's pretty much the default if your VM's are using DHCP.
>
> The one thing to recall is, and this is from memory, is that "host" and
"dig" don't make use of the
> system's resolver library. They query dns servers directly. So, another thing to
check is if the
> /etc/nsswitch.conf on the VM's are the same as the host.
>
Dig did not work either.
function GetPublicIP () {
local WIP=$(dig +short
myip.opendns.com @resolver1.opendns.com)
# echo "WIP = <$WIP>" > "/dev/tty"
if [[ "$WIP" == *"not found"* || "$WIP" == *"no
servers could be reached"* ]]; then
WIP="Not Found"
fi
echo $WIP
}
_______________________________________________
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.
--
Remind me to ignore comments which aren't germane to the thread.