[Bug 1818634] [NEW] resolvconf does not work well if using networkd but not resolved

[Johnny Come Lately]

Public bug reported:

I'm running Ubuntu Server 18.04, which uses systemd-networkd.  If I
install resolvconf and disable systemd-resolved, resolvonf keeps putting
"nameserver 127.0.0.53" in /etc/resolv.conf.  To get rid of that
behavior, I disabled resolvconf-pull-resolved.path.  Now resolvconf
doesn't put any nameservers in /etc/resolv.conf, even though networkd's
DHCP client has correctly stored the DNS server in /run/systemd/* and
it's also available via "networkctl status".

In short, resolvconf has support for dhclient and systemd-resolved, but
no support for systemd-networkd without systemd-resolved.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: resolvconf 1.79ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Tue Mar  5 03:15:02 2019
InstallationDate: Installed on 2019-03-04 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
SourcePackage: resolvconf
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.dhcp.dhclient-enter-hooks.d.resolvconf: [modified]
mtime.conffile..etc.dhcp.dhclient-enter-hooks.d.resolvconf: 2019-03-05T03:09:13.709323

** Affects: resolvconf (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  resolvconf does not work well if using networkd but not resolved

Status in resolvconf package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu Server 18.04, which uses systemd-networkd.  If I
  install resolvconf and disable systemd-resolved, resolvonf keeps
  putting "nameserver 127.0.0.53" in /etc/resolv.conf.  To get rid of
  that behavior, I disabled resolvconf-pull-resolved.path.  Now
  resolvconf doesn't put any nameservers in /etc/resolv.conf, even
  though networkd's DHCP client has correctly stored the DNS server in
  /run/systemd/* and it's also available via "networkctl status".

  In short, resolvconf has support for dhclient and systemd-resolved,
  but no support for systemd-networkd without systemd-resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Mar  5 03:15:02 2019
  InstallationDate: Installed on 2019-03-04 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.dhcp.dhclient-enter-hooks.d.resolvconf: [modified]
  mtime.conffile..etc.dhcp.dhclient-enter-hooks.d.resolvconf: 2019-03-05T03:09:13.709323

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