Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Does a basic Pi installation use dnsmasq or systemd.resolvd?

620 views
Skip to first unread message

Chris Green

unread,
Dec 1, 2021, 4:33:04 PM12/1/21
to
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?

--
Chris Green
·

Martin Gregorie

unread,
Dec 1, 2021, 5:30:15 PM12/1/21
to
On Wed, 1 Dec 2021 21:30:53 +0000, 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?

My (running but unusable, headless) Pi 2B with bullseye installed as an
in-situ upgrade has systemd-resolve in /usr/bin but the datestamp shows
it was inherited from buster.

HTH


--

--
Martin | martin at
Gregorie | gregorie dot org

A. Dumas

unread,
Dec 1, 2021, 7:24:28 PM12/1/21
to
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:

$ resolvectl status
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service
not found

$ service systemd-resolved.service status
Unit systemd-resolved.service.service could not be found.

Debian has this:
https://wiki.debian.org/NetworkConfiguration#Defining_the_.28DNS.29_Nameservers

The Natural Philosopher

unread,
Dec 2, 2021, 3:39:45 AM12/2/21
to
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.


--
Outside of a dog, a book is a man's best friend. Inside of a dog it's
too dark to read.

Groucho Marx


zeneca

unread,
Dec 2, 2021, 4:51:44 AM12/2/21
to
Le 1/12/21 à 22:30, Chris Green a écrit :
> 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?
>

Have a look at /etc/nsswitch.conf

Chris Green

unread,
Dec 2, 2021, 5:03:04 AM12/2/21
to
The Natural Philosopher <t...@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 ....

--
Chris Green
·

Chris Green

unread,
Dec 2, 2021, 5:33:03 AM12/2/21
to
... 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
·
0 new messages