Chris Green <
cl@isbd.net> wrote:
The Natural Philosopher <tnp@invalid.invalid> wrote:
On 02/12/2021 00:24, A. Dumas wrote:
On 01-12-2021 22:30, Chris Green wrote:
To avoid having to do a clean install myself does anyone know if an
"out of the box" installation of Raspberry Pi OS uses dnsmasq or
systemd.resolvd for DNS?
Neither, I think, but I'm not 100% sure how to check. Aren't both local DNS caching servers? This is on a fresh RaspiOS Bullseye Lite 64-bit:
I could find no evidence of a caching nameserver on my Pi...it picks up
a nameserver in my case from a static definition in /etc/resolv.conf and that is it.
OK, thanks all, I've decided to bite the bullet and write a new SD
card (very old Pi) with a fairly recent Pi image and install it and
take a look myself.
Listen to this space ....
... and the answer is that TNP is absolutely right, there's no caching
(or is it cacheing) nameserver installed by default on a Pi.
Ah, no, not quite. The systemd-resolved.service is installed but it's
not activated by default:-
root@raspberrypi:~# systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/systemd-resolved.service.d
└─resolvconf.conf
Active: inactive (dead)
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolved
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Actually isn't that slightly worrying, it says "vendor preset: enabled" which suggests
that it's supposed to be enabled but something has disabled it.
--
Chris Green
·
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)