I did notice when poking around that compared to another Debian based device, there weren’t some equivalent files under /run/... Anyways, I checked the status with:
systemctl status systemd-resolved
Which indicated it was disabled &inactive/dead:
systemd-resolved.service -Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
Active: inactive (dead)
etc…
To fix this I enabled and started the service:
sudo systemctl enable systemd-resolved.service
sudo systemctl start systemd-resolved.service
Which got it back running as it likely should be:
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: active (running) since ...
etc…
I linked the two files with:
sudo ln -sf /run/sysemd/resolve/stub-resolv.conf /etc/resolv.conf
I confirmed that these two now mirror each other, however nameserver 127.0.0.53 isn’t working to resolve DNS queries to allow the browser to connect, which suggests something else is wrong.
Additionally, on my other Debian-based device, it doesn’t seem to have these symbolically linked. /run/sysemd/resolve/stub-resolv.conf has nameserver 127.0.0.53 listed, but `/etc/resolv.conf has the nameservers assigned from the router via NetworkManager.
After running
sudo systemctl restart systemd-resolved.service
resolvedctl status
I get:
Global
Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub
Which should be set to foreign instead of stub to get from the router. I also have below that:
Link2 (eno0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link4 (lxcbr0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link5 (ipv6leakintrf0)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
DNS Servers: ::1
DNS Domain: ~.
Link 10 (wls6)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
No sign of wlan0 or eth0, which I would’ve expected somewhere in there…