** No longer affects: resolvconf (Ubuntu Trusty)
** No longer affects: resolvconf (Ubuntu Xenial)
** No longer affects: systemd (Ubuntu Trusty)
** No longer affects: systemd (Ubuntu Xenial)
** No longer affects: systemd (Ubuntu)
** No longer affects: systemd (Ubuntu Cosmic)
** No longer
This bug was fixed in the package resolvconf - 1.79ubuntu10.18.04.3
---
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.
This bug was fixed in the package resolvconf - 1.79ubuntu10.18.10.3
---
resolvconf (1.79ubuntu10.18.10.3) cosmic; urgency=medium
* d/resolvconf.resolvconf-pull-resolved.service
Hack out the 'edns0' option that systemd-resolved has
recently added to its stub-resolv.conf.
ubuntu@lp1817903-c:~$ dpkg -l |grep resolvconf
ii resolvconf 1.79ubuntu10.18.10.2 all
name server information handler
ubuntu@lp1817903-c:~$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic
I have installed 1.79ubunbtu10.18.04.3 from the bionic-proposed and
rebooted...
The result is different from before
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
#
Hello Steve, or anyone else affected,
Accepted resolvconf into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.79ubuntu10.18.10.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Changed in: resolvconf (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
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/1817903
Title:
systemd-resolve
** Description changed:
[impact]
systems upgraded from pre-Bionic releases to Bionic or later will
continue to use ifupdown/resolvconf for network conf and management, but
resolvconf has a new systemd service in Bionic and later that pulls
systemd-resolved stub-resolv.conf into its
Previous change reverted and new fix uploaded (after ddstreet discussion
with xnox) in Disco.
- Eric
** Changed in: resolvconf (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Tags added: patch
--
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/1817903
Title:
systemd-resolve appends "options edns0" to resolv.conf
Status in resolvconf package in
** Patch added: "lp1817903-disco.debdiff"
https://bugs.launchpad.net/ubuntu/disco/+source/resolvconf/+bug/1817903/+attachment/5246425/+files/lp1817903-disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
** Changed in: resolvconf (Ubuntu Cosmic)
Status: Triaged => In Progress
** Changed in: resolvconf (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: resolvconf (Ubuntu Disco)
Status: Fix Released => In Progress
--
You received this bug notification because you
The resolvconf SRU also introduces regressions (LP: #1819625) and is in
the process of being reverted.
** Changed in: resolvconf (Ubuntu Bionic)
Status: Fix Released => Triaged
** Changed in: resolvconf (Ubuntu Cosmic)
Status: Fix Released => Triaged
--
You received this bug
Thanks, that solved it. Not sure why I had both at all, never fiddled on
this low level stuff. Must be a left-over from some Ubuntu upgrade in
the past that was now triggered by this patch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
> man systemd-resolved has the following line:
If this update had any effect on you, then you're not using systemd-
resolved; you're using resolvconf. If you don't want that, then
uninstall resolvconf, and your dns resolution will revert to using
systemd-resolved.
--
You received this bug
I just got this update on Ubuntu 18.10 and it broke resolving of
localhost subdomains. localhost can be resolved to 127.0.0.1, but any
*.localhost can not.
man systemd-resolved has the following line:
The hostnames "localhost" and "localhost.localdomain" (as well as any
hostname ending in
This bug was fixed in the package resolvconf - 1.79ubuntu10.18.04.1
---
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.
This bug was fixed in the package resolvconf - 1.79ubuntu10.18.10.1
---
resolvconf (1.79ubuntu10.18.10.1) cosmic; 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.
cosmic:
ubuntu@lp1817903-x-b-c:~$ dpkg -l |grep resolvconf
ii resolvconf1.79ubuntu10 all
name server information handler
ubuntu@lp1817903-x-b-c:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
bionic:
ubuntu@lp1817903-x-b:~$ dpkg -l | grep resolvconf
ii resolvconf1.79ubuntu10 all
name server information handler
ubuntu@lp1817903-x-b:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
I can confirm that the update from proposed solves the problem.
--
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/1817903
Title:
systemd-resolve appends "options edns0" to
Installed resolvconf from bionic-proposed, all seems to working as it
should.
--
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/1817903
Title:
systemd-resolve appends
Sorry, my bad, it seems I miss read the first part of the wiki! Now
installed, will report back.
--
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/1817903
Title:
ports.ubuntu.com is NOT a mirror of the main archive, it's a separate
distribution channel for less-common architectures.
If in doubt, use archive.ubuntu.com.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
On checking it seems that is the case. Tried a dozen different mirrors all give:
Failed to fetch
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/binary-amd64/Packages
404 Not Found [IP: 91.189.88.150 80]
Which mirror do you recommend?
--
You received this bug notification
On Sat, Mar 02, 2019 at 11:33:13AM -, Steve Roberts wrote:
> I followed the instructions at
> https://wiki.ubuntu.com/Testing/EnableProposed
> but after repeated updates, it keeps telling me the it is not found:
> $ sudo apt-get install resolvconf/bionic-proposed
> Reading package lists...
I followed the instructions at
https://wiki.ubuntu.com/Testing/EnableProposed
but after repeated updates, it keeps telling me the it is not found:
$ sudo apt-get install resolvconf/bionic-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
E:
Hello Steve, or anyone else affected,
Accepted resolvconf into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.79ubuntu10.18.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Description changed:
[impact]
systems upgraded from pre-Bionic releases to Bionic or later will
continue to use ifupdown/resolvconf for network conf and management, but
resolvconf has a new systemd service in Bionic and later that pulls
systemd-resolved stub-resolv.conf into its
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu Cosmic)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu Disco)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu Bionic)
Importance: Critical =>
This bug was fixed in the package resolvconf - 1.79ubuntu11
---
resolvconf (1.79ubuntu11) disco; 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
** Also affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: resolvconf (Ubuntu Disco)
Importance: Undecided => High
** Changed in: resolvconf (Ubuntu Disco)
Status: New => In Progress
** Changed in: resolvconf (Ubuntu Disco)
Assignee:
> $ sudo systemctl enable resolvconf-pull-resolved.service
> this gives: The unit files have no installation config
yes that's fine, sorry - this .service can't be enabled/disabled, it's
just triggered by the .path service. I should have left out the
'disable' of it in my first instructions
Testing fix:
I added the ppa (same system) and updated resolvconf
then did:
$ sudo systemctl enable resolvconf-pull-resolved.path
OK
and
$ sudo systemctl enable resolvconf-pull-resolved.service
this gives: The unit files have no installation config
(not sure if this is expected ?), but it
@xnox adding you to this bug fyi.
--
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/1817903
Title:
systemd-resolve appends "options edns0" to resolv.conf
Status in systemd
@brian-murray since you commented in comment 3 and thus are familiar
with this bug, and I don't have disco upload rights, please give my MP a
look and merge into disco if you have a chance. I'll SRU to B/C once
it's in D. Thanks.
--
You received this bug notification because you are a member
@drgrumpy can you test the resolvconf package from this ppa to see if it
correctly fixes the problem for you (on a system where you haven't
worked around this by disabling the 'resolvconf-pull-resolved'
service/path, of course):
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1817903
**
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Disco)
Importance: Critical
Assignee: Dan Streetman (ddstreet)
Status: In
** Description changed:
+ [impact]
+
+ systems upgraded from pre-Bionic releases to Bionic or later will
+ continue to use ifupdown/resolvconf for network conf and management, but
+ resolvconf has a new systemd service in Bionic and later that pulls
+ systemd-resolved stub-resolv.conf into its
> But in the long term I guess I should move to systemd-networkd as the
> preferred way to set static ip?
that is entirely up to your preferences; ifupdown and resolvconf are
still supported, and included, and you can continue to use them. They
are still the default way to configure the network
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/resolvconf/+git/resolvconf/+merge/363748
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Yes that works, and many thanks for the explanation.
/etc/resolv.conf is now linked to /run/resolvconf/resolv.conf
and contains only the local proxy dns:
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND --
> I do not use NetworkManager as I use fixed ip, so the ip, etc. and dns is/was
> specified in /etc/network/interfaces
ah, ok, so you are not using systemd-networkd then, ok that makes sense
since you upgraded from pre-bionic where ifupdown/resolvconf are the
default. In bionic they have been
Thanks again for the help
Removed resolvconf:
sudo apt remove resolvconf
reboot
as expected now /etc/resolv.conf is linked to run/systemd/sub-resolv.conf
and contains only:
nameserver 127.0.0.53
options edns0
BUT now I cannot connect to anything, nslookup, ping fails, etc.
$ ping
Thanks for the attention to this:
DNS servers: 208.67.220.220 (opend dns) and 212.159.6.10 (recommended by
isp)
typical sites: planthealth.co.uk, plus random others...
nslookup and dig ok
ping domain_name gives "Name or service not known"
ping ip ok
FF: Hmmm problem etc...
So this is my
Ok I have found what the problem is, I think; I suspect that you have
resolvconf installed on your system, which is taking over the
/etc/resolv.conf file, and I think that resolvconf is pulling the edns0
option, but also including external nameserver(s), which is an incorrect
configuration, since
@downgrade, basically
$ dpkg -l | grep 237-3ubuntu10
-> that should give you the list of systemd debs installed
download those from https://bugs.launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+build/16258134
and use 'sudo dpkg -i *.deb'
--
You received this bug notification
> in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)
in Bionic, resolv.conf links (by default) to /run/systemd/resolve/stub-
resolv.conf; is that what you meant?
Can you paste the contents of your /etc/resolv.conf file here?
--
You received this bug notification because you are a
Could you give some examples of DNS lookups that fail for you so we can
try and recreate the issue? Additionally, do you know what DNS servers
you are using?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
My update was from 237-3ubuntu10.11, which didn't have the problem (12
was never installed)
It seems I cannot easily downgrade via apt or synaptic, as the previous
versions do not seem to be in the repos, can you advise how to do so?
On a different machine on the same network I still have
Thank you for your bug report, did you try to downgrading the system packages
to see if that resolves the issue?
The previous update has change in dns queries
https://bugs.launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.12
Would be interesting to know if that version already had the problem?
51 matches
Mail list logo
