💾 Archived View for gemini.susa.net › resolvconf_and_systemd_resolver.gmi captured on 2022-06-03 at 23:26:22. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
On Debian,
~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
The above will show if your 'resolv.conf' is managed by 'resolvconf'.
Now let's ensure we've got our local systemd resolver configured.
~$ vi /etc/systemd/resolved.conf [Resolve] DNS=192.168.178.1 (e.g. your local DNS server, possibly your router) Cache=yes ~$ systemctl restart systemd-resolved.service
Finally, for completeness, ensure resolvconf has the chance to generate 'resolv.conf', though this has probably already been done.
For reference, the name and location of the resolvconf files are also shown below.
cat resolv.conf.d/{base,head,original,tail} service resolvconf restart