Host name resolution fails on Fedora 39 system
0
votes
1
answer
531
views
One of my Fedora systems will often fail to do DNS resolution. Both
ping host.ext
and nslookup host.ext
fail.
When I edit /etc/resolv.conf
to use nameserver 1.1.1.1
instead of nameserver 127.0.0.53
, nslookup works, but ping still fails.
Why is the runtime library not using the nameserver listed in /etc/resolv.conf
?
/etc/nsswitch.conf
contains
# Generated by authselect
# Do not modify this file manually, use authselect instead. Any user changes will be overwritten.
# You can stop authselect from managing your configuration by calling 'authselect opt-out'.
# See authselect(8) for more details.
# In order of likelihood of use to accelerate lookup.
passwd: files sss systemd
shadow: files
group: files sss systemd
hosts: files myhostname resolve [!UNAVAIL=return] dns
services: files sss
netgroup: files sss
automount: files sss
aliases: files
ethers: files
gshadow: files
networks: files dns
protocols: files
publickey: files
rpc: files
How do I fix that?
How do I persuade the local named to forward its requests to an external name server?
Linux has acquired all these little "helpful" modules, but it seems to me they just obfuscate situations such as these.
Asked by Lars Poulsen
(357 rep)
Apr 4, 2024, 11:11 PM
Last activity: Apr 8, 2024, 11:27 PM
Last activity: Apr 8, 2024, 11:27 PM