[Bug 1735296] Re: systemd-resolved.service

[Dimitri John Ledkov]

Correct, purging resolvconf is only supported "out of the box"/"just
works" in 17.10 and up, as resolvconf/libnss-resolve there have the
correct maintainer scripts to do the tansition.

I do not recommend using systemd-resolve in xenial, as it does not have
a stub resolver available, and software that does not use nss will not
be able to have any network resolution without bypassing resolved. Using
systemd-resolved without resolvconf is currently only best supported on
17.10+.

** Changed in: systemd (Ubuntu)
       Status: New => Confirmed

** Summary changed:

- systemd-resolved.service
+ systemd-resolved.service doesn't play nice if resolvconf is removed on xenial, works on artful+

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1735296

Title:
  systemd-resolved.service doesn't play nice if resolvconf is removed on
  xenial, works on artful+

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  if you purge resolvconf on Xenial and want systemd-resolve the link is
  not update and its doesn't use systemd-resolce cache

  1) 
  Description:    Ubuntu 16.04.3 LTS
  Release:        16.04

  2) systemd  229-4ubuntu21  amd64  system and service manager

  3)
  ls -l /etc/resolv.conf
  lrwxrwxrwx 1 root root 29 Nov 29 22:40 /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  aptitude purge -y resolvconf

  ########

  ls -l /run/systemd/resolve
  total 4
  -rw-r--r-- 1 systemd-resolve systemd-resolve 381 Nov 29 22:42 resolv.conf

  ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf

  # on it's working
  Description:    Ubuntu Bionic Beaver (development branch)
  Release:        18.04
  systemd --version
  235

  ls -l /run/systemd/resolve/
  total 8
  -rw-r--r-- 1 systemd-resolve systemd-resolve 608 Nov 29 16:36 resolv.conf
  -rw-r--r-- 1 systemd-resolve systemd-resolve 264 Nov 29 16:36 stub-resolv.conf

  ls -l /etc/resolv.conf
  lrwxrwxrwx 1 root root 39 Oct 25 10:38 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

  
  4)
  ########## 
  ls -l /etc/resolv.conf
  lrwxrwxrwx 1 root root 29 Nov 29 22:40 /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  systemctl status/restart systemd-resolved.service

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