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

    From Chris Green@21:1/5 to All on Wed Dec 1 21:30:53 2021
    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
    ·

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Gregorie@21:1/5 to Chris Green on Wed Dec 1 22:30:14 2021
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From A. Dumas@21:1/5 to Chris Green on Thu Dec 2 01:24:26 2021
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From The Natural Philosopher@21:1/5 to A. Dumas on Thu Dec 2 08:39:43 2021
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Green@21:1/5 to The Natural Philosopher on Thu Dec 2 09:49:12 2021
    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 ....

    --
    Chris Green
    ·

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From zeneca@21:1/5 to All on Thu Dec 2 10:51:37 2021
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Green@21:1/5 to Chris Green on Thu Dec 2 10:26:08 2021
    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: fsxNet Usenet Gateway (21:1/5)