> Flexibility for flexibility's sake is not a goal of Ubuntu.

Hmmmm...flexibility for the sake of making a system work seems like a
good goal. As a user of Linux for 18 years, and one that has used Ubuntu
since its very first release, I can say with confidence that Linux is
absolutely about choice and flexibility. Any distro that forgets this
fact has limited or short-lived success.

> resolved is not configured as a caching nameserver; it is a stub resolver,
> configured for the purpose of ensuring a stable DNS endpoint.

Perhaps I've conflated resolved with the NetworkManager dnsmasq
instance, which is most definitely configured as a caching resolver (and
the first iteration of this type of default setup in Ubuntu, also a
nightmare for crusty old *nix users). My understanding, based on the
documentation, is that resolved acts as a caching resolver. systemd-
resolved.server(8) states very clearly:

"systemd-resolved is a system service that provides network name
resolution to local applications. It implements a caching and validating
DNS/DNSSEC stub resolver, as well as an LLMNR resolver and responder."

> Enabling a local resolver on servers in addition to desktops (where we have
> already enabled dnsmasq for years) has been a common request.

Consider this a request to allow an Ubuntu system to work without
dnsmasq or any other local caching resolver. I'm sure it's not the first
nor the last.

There are definitely scenarios where running dsnmasq as a local
(caching?) resolver is inappropriate and I'm happy to give a few
scenarios, but that's not what _this_ _bug_ is about. This bug is about
a defect in the resolvconf and resolved dhclient integration scripts.

Philosophical discussion aside, I have reported a valid bug that will
definitely affect some number of Ubuntu users. I've also provided a
safe, simple, straightforward fix to this bug. It's an improvement to
the software.

Unless the fix is technically unsound,  there is absolutely no reason
not to implement it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1745463

Title:
  Disabling systemd-resolved breaks dhclient resolvconf integration

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  To reproduce, mask resolved:
  sudo systemctl mask systemd-resolved.service

  ...then disable network-manager for ifupdown interfaces:
  $cat /etc/NetworkManager/NetworkManager.conf              
  [main]
  plugins=ifupdown,keyfile
  dns=default
  rc-manager=resolvconf

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  ...and reboot.

  You'll note that resolvconf integration with dhclient is now broken.
  Interfaces listed in /etc/network/interfaces or
  /etc/network/interfaces.d/* will not provide DNS configuration in
  /etc/resolv.conf and /run/resolvconf/interfaces/.

  This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines
  "make_resolv_conf()" as a valid function for the BOUND case, but
  /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty
  now, eh?) even though resolved is masked.

  The file existence check in the beginning of /etc/dhcp/dhclient-enter-
  hooks.d/resolved should be more thorough, i.e. it should ensure that
  resolved is enabled, rather than simply look for the existence of
  /lib/systemd/systemd-resolved. This works for me:

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled 
systemd-resolved ; then

  Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement
  a similar check, looking for /run/resolvconf/enable-updates as a
  condition for meddling with DNS settings. If desired, I'll file a
  separate bug for that package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to