[kwlug-disc] Systemd resolv issue ...

[Khalid Baheyeldin]

Thanks for the responses, I really appreciate it.

Note: The problem was solved, see the last paragraph of this email.
Frustratingly though: I don't know why things weren't working.

Output from resolvectl, minus the unused interfaces ...

Global
        Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
 resolv.conf mode: stub

Link 3 (enp3s0)
   Current Scopes: DNS
        Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS
DNSSEC=no/unsupported
Current DNS Server: 192.168.0.1
      DNS Servers: 192.168.0.1
       DNS Domain: lan

Link 11 (wg0)
   Current Scopes: DNS
        Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS
DNSSEC=no/unsupported
Current DNS Server: 10.10.0.1
      DNS Servers: 10.10.0.1
       DNS Domain: ~.

The /etc/resolv.conf links to the right place ...

ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Aug 27  2024 /etc/resolv.conf ->
../run/systemd/resolve/stub-resolv.conf

And its contents (minus comments at the top)

nameserver 127.0.0.53
options edns0 trust-ad
search lan

Resolvectl times out:

$ resolvectl query google.com
google.com: resolve call failed: Query timed out


DNS servers are the router (192.168.0.1), and for the Wireguard VPN
connection, it is the VPN gateway itself.

$ resolvectl | grep 'DNS Serv'
Current DNS Server: 192.168.0.1
      DNS Servers: 192.168.0.1
Current DNS Server: 10.10.0.1
      DNS Servers: 10.10.0.1

Interestingly, from the botched machine, the Wireguard VPN gateway can be
pinged (using its IP address), and I can access HTTP on it too.

Finally, when I restarted the VPN:

sudo systemctl restart wg-quick at wg0

Things started working normally again ...
Sadly, I don't know why all that happened, nor how to solve it the next
time.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kwlug.org/pipermail/kwlug-disc_kwlug.org/attachments/20260211/7e8e5d56/attachment.htm>