:: Re: [DNG] Danger: Debian POSIX host…
Top Page
Delete this message
Reply to this message
Author: Mason Loring Bliss
Subject: Re: [DNG] Danger: Debian POSIX hostility
On Wed, Sep 16, 2020 at 08:45:06AM -0400, Hendrik Boom wrote:

> On Wed, Sep 16, 2020 at 02:11:57AM -0400, Steve Litt wrote:
> >
> > Speaking of Netowrk manager, am I the only one who hates it messing
> > with /etc/resolv.conf?
> No. You are not the only one.

I prefer ifupdown, but I like Network Manager for laptops. This particular
behaviour can be managed, which is useful for me given that I have various
ways I need to manage resolv.conf on different systems.

For what it's worth, here's an excerpt from the NetworkManager.conf(5) man
page - take special note of the last paragraph:

           Set the DNS (resolv.conf) processing mode. If the key is
           unspecified, default is used, unless /etc/resolv.conf is a symlink
           to /run/systemd/resolve/stub-resolv.conf,
           /run/systemd/resolve/resolv.conf, /lib/systemd/resolv.conf or
           /usr/lib/systemd/resolv.conf. In that case, systemd-resolved is
           chosen automatically.

           default: NetworkManager will update /etc/resolv.conf to reflect the
           nameservers provided by currently active connections.

           dnsmasq: NetworkManager will run dnsmasq as a local caching
           nameserver, using a "split DNS" configuration if you are connected
           to a VPN, and then update resolv.conf to point to the local
           nameserver. It is possible to pass custom options to the dnsmasq
           instance by adding them to files in the
           "/etc/NetworkManager/dnsmasq.d/" directory. Note that when multiple
           upstream servers are available, dnsmasq will initially contact them
           in parallel and then use the fastest to respond, probing again
           other servers after some time. This behavior can be modified
           passing the 'all-servers' or 'strict-order' options to dnsmasq (see
           the manual page for more details).

           unbound: NetworkManager will talk to unbound and dnssec-triggerd,
           providing a "split DNS" configuration with DNSSEC support.
           /etc/resolv.conf will be managed by dnssec-trigger daemon.

           systemd-resolved: NetworkManager will push the DNS configuration to

           none: NetworkManager will not modify resolv.conf. This implies
           rc-manager unmanaged

Mason Loring Bliss          mason@???          Ewige Blumenkraft!
awake ? sleep : random() & 2 ? dream : sleep; -- Hamlet, Act III, Scene I