-
resolvconf (1.79ubuntu10.18.04.3) bionic; urgency=medium
* d/resolvconf.resolvconf-pull-resolved.service
Hack out the 'edns0' option that systemd-resolved has
recently added to its stub-resolv.conf. (LP: #1817903)
-- Dan Streetman <email address hidden> Thu, 14 Mar 2019 17:35:23 -0400
-
resolvconf (1.79ubuntu10.18.04.2) bionic; urgency=medium
* Revert the previous SRU, which regressed DNS handling in certain
configurations. LP: #1819625.
-- Steve Langasek <email address hidden> Wed, 13 Mar 2019 14:15:36 -0700
-
resolvconf (1.79ubuntu10.18.04.1) bionic; urgency=medium
* Pull systemd-resolved conf from non-stub file; the stub file should
not be used unless all dns traffic goes to the local stub resolver.
Specifically, now that stub-resolv.conf includes edns0 option,
using the stub conf with non-local dns servers can break dns
resolution. (LP: #1817903)
-- Dan Streetman <email address hidden> Wed, 27 Feb 2019 17:03:57 -0500
-
resolvconf (1.79ubuntu10) bionic; urgency=medium
* Fix race of not injecting resolved config into resolvconf on LXD
container boot. LP: #1763108
-- Dimitri John Ledkov <email address hidden> Thu, 12 Apr 2018 12:46:24 +0100
-
resolvconf (1.79ubuntu9) bionic; urgency=medium
* Move resolvconf & resolved integration system units from src:systemd
to src:resolvconf. Also use a different unit name, to avoid
breaks/replaces.
-- Dimitri John Ledkov <email address hidden> Tue, 30 Jan 2018 14:17:27 +0000
-
resolvconf (1.79ubuntu8) artful; urgency=medium
* Dereference /etc/resolf.conf when creating runtime configuration when
migrating to resolvconf managed /etc/resolv.conf. The contents of
/etc/resolv.conf (rather than the symlink target information) is
needed in /run/resolvconf/resolv.conf and
/run/resolvconf/interface/original.resolvconf during migration until
resolvconf updates the config next. LP: #1713149
-- Dimitri John Ledkov <email address hidden> Tue, 29 Aug 2017 14:04:33 +0100
