[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-10-08 Thread Jez
I'm experiencing this issue with Ubuntu 19.04 resolvconf version: 1.79ubuntu13 Oct 6 21:30:19 miranda systemd[1]: Failed to start resolvconf-pull-resolved.service. Oct 6 21:30:19 miranda systemd[1]: resolvconf-pull-resolved.service: Start request repeated too quickly. Oct 6 21:30:19 miranda

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-14 Thread Launchpad Bug Tracker
This bug was fixed in the package resolvconf - 1.79ubuntu10.18.04.2 --- resolvconf (1.79ubuntu10.18.04.2) bionic; urgency=medium * Revert the previous SRU, which regressed DNS handling in certain configurations. LP: #1819625. -- Steve Langasek Wed, 13 Mar 2019 14:15:36 -070

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-14 Thread Rafał Harabień
I had troubles with DNS resolution in last days after reboot and I think it may be related to resolvconf package update. I spotted following entries in resolvconf-pull-resolved.service journal: mar 14 09:30:01 *** systemd[1]: resolvconf-pull-resolved.service: Start request repeated too quickly. m

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-14 Thread Launchpad Bug Tracker
This bug was fixed in the package resolvconf - 1.79ubuntu10.18.10.2 --- resolvconf (1.79ubuntu10.18.10.2) cosmic; urgency=medium * Revert the previous SRU, which regressed DNS handling in certain configurations. LP: #1819625. -- Steve Langasek Wed, 13 Mar 2019 14:15:36 -070

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-13 Thread Bruno
@ddstreet: > are you upstream nameservers not reachable from your system? upstream servers have no clue about local LXC/LXD (linuxcontainers.org) DNS names. Configuration basically done via systemd-resolve --interface lxdbr0 --set-dns 10.145.28.1 --set-domain lxd This gets broken by the update.

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-13 Thread Steve Langasek
Hello Boris, or anyone else affected, Accepted resolvconf into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/resolvconf/1.79ubuntu10.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. Se

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-13 Thread Steve Langasek
Hello Boris, 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.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. Se

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-13 Thread Steve Langasek
On a desktop system continuously upgraded from pre-xenial (through non- LTS releases), I have the following before upgrade: $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 27 Mar 29 2012 /etc/resolv.conf -> /run/resolvconf/resolv.conf $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for gli

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-13 Thread Dan Streetman
@bruno-42 are you upstream nameservers not reachable from your system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819625 Title: Package resolvconf=1.79ubuntu10.18.04.1 broken To manage notifica

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-13 Thread Steve Langasek
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819625 Title: Package resolvconf=1.79ubuntu10.18.04.1 broken To manage notifications about this bug go to: https://bu

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-13 Thread Bruno
No vpn - DNS resolver broken by update (on production server) bug@test:~$ 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 # 127.0.0.53 is the systemd-resolved stub resolver.

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-12 Thread Boris Vulikh
For the affected, a workaround is available: Download and manually install resolveconf from the previous version-1.79ubuntu10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819625 Title: Package res

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: resolvconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819625 Title:

[Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken

2019-03-12 Thread Caiwyn
Can confirm. Specifically breaks DNS resolution in Firefox when I'm logged into an OpenConnect VPN. I can resolve hosts that are in public DNS, but I'm uncertain if this is because of caching. Internal DNS over the VPN no longer resolves. Downgrading to the previous version of resolvconf restor