May I backtrack a bit, and ask how is this system configured? And is it
a desktop or a server configuration? Is it a fresh install or an

Specifically, what I am confused about is how the networking is
configured and where /etc/resolv.conf is pointing at.

I see that NetworkManager and ifupdown were mentioned. Do you have both
of these configured and try to manage a) networking b) /etc/resolv.conf?

And what are the steps to reproduce this? Ideally with something simple
and reproducible like a lxd container launched with $ lxd launch ubuntu-
daily:artful test-container

Note that overriding make_resolv_conf() is a good thing, and it should
not at all be used. None of our network configuration tools rely on
make_resolv_conf() which is an extremely bad interface that writes out a
static file and looses information, as it assumes that there is only
ever one interface and one dhcp. Hence you will notice that everything
(networkd+resolved, ifupdown+resolvconf, networkmanager) overridee

I'm not quite sure what was done to your system, but resolvconf can be
used to managed the /etc/resolv.conf and that is integrated with
resolved. You will notice that resolved stub nameserver is pulled into
resolvconf config, and thus resolvconf can own /etc/resolv.conf which is
what happens on upgrades.

Please update the bug description on how to reproduce the problem you
are seeing, without ranting or jumping to conclusions, or trying to make
any unnecessary changes, because it is hard to understand what you are
trying to achieve, which may have been made worse with unnecessary

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

** Changed in: resolvconf (Ubuntu)
       Status: New => Incomplete

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  Disabling systemd-resolved breaks dhclient resolvconf integration

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to