My machine is no longer able to find a DNS server. It appears to have started after first running a docker container (bound to 127.0.0.1:port i think), but this could be a coincidence.
In other words: host hostname times out but host -a hostname 192.168.1.1 works fine.
192.168.1.1 is the gateway and dns server it should have picked up from its DHCP server.
$ sudo resolvectl status
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (eno1)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
DNS Servers: 192.168.1.1
DNS Domain: home
Link 3 (br-e088e4cb0c17)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 4 (docker0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
other computers on the network can pull DNS from from 192.168.1.1 fine. THe system having a problem can ping 192.168.1.1
/etc/resolve.conf/ is symlinked to /run/systemd/resolve/stub-resolv.conf
i havn't changed this. The content of that file is
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# ...more lines snipped....
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0 trust-ad
search home
systemd-resolved shows something odd, but I don't understand it very well.
$ systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2023-01-22 19:14:25 UTC; 15min ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 645 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 9274)
Memory: 8.4M
CPU: 139ms
CGroup: /system.slice/systemd-resolved.service
└─645 /lib/systemd/systemd-resolved
Jan 22 19:30:06 lenovom900 systemd-resolved[645]: Got packet on unexpected (i.e. non-localhost) IP range, ignoring.
Jan 22 19:30:06 lenovom900 systemd-resolved[645]: Got packet on unexpected (i.e. non-localhost) IP range, ignoring.
Jan 22 19:30:11 lenovom900 systemd-resolved[645]: Got packet on unexpected (i.e. non-localhost) IP range, ignoring.
Jan 22 19:30:11 lenovom900 systemd-resolved[645]: Got packet on unexpected (i.e. non-localhost) IP range, ignoring.
Jan 22 19:30:12 lenovom900 systemd-resolved[645]: Got packet on unexpected (i.e. non-localhost) IP range, ignoring.
Jan 22 19:30:16 lenovom900 systemd-resolved[645]: Got packet on unexpected (i.e. non-localhost) IP range, ignoring.
Jan 22 19:30:16 lenovom900 systemd-resolved[645]: Got packet on unexpected (i.e. non-localhost) IP range, ignoring.
Jan 22 19:30:17 lenovom900 systemd-resolved[645]: Got packet on unexpected (i.e. non-localhost) IP range, ignoring.
Jan 22 19:30:21 lenovom900 systemd-resolved[645]: Got packet on unexpected (i.e. non-localhost) IP range, ignoring.
Jan 22 19:30:21 lenovom900 systemd-resolved[645]: Got packet on unexpected (i.e. non-localhost) IP range, ignoring.
finally
$ ip route
default via 192.168.1.1 dev eno1 proto dhcp src 192.168.1.200 metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.200 metric 100
192.168.1.1 dev eno1 proto dhcp scope link src 192.168.1.200 metric 100
What happened and how can this be fixed?
