| 2016-01-20 13:11:29 |
Jonathan Kamens |
bug |
|
|
added bug |
| 2016-01-20 21:14:52 |
Thomas Hood |
bind9 (Ubuntu): status |
New |
Incomplete |
|
| 2016-01-20 21:27:29 |
Jonathan Kamens |
bind9 (Ubuntu): status |
Incomplete |
New |
|
| 2016-05-03 17:37:37 |
ilia |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744304 |
|
| 2016-05-03 17:37:37 |
ilia |
attachment added |
|
bind9-resolvconf.patch https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1536181/+attachment/4654702/+files/bind9-resolvconf.patch |
|
| 2016-05-03 17:39:12 |
ilia |
bug task added |
|
bind9 (Debian) |
|
| 2016-05-03 20:02:38 |
Bug Watch Updater |
bind9 (Debian): status |
Unknown |
New |
|
| 2016-05-03 20:24:05 |
Ubuntu Foundations Team Bug Bot |
tags |
amd64 apport-bug wily |
amd64 apport-bug patch wily |
|
| 2016-05-03 20:24:15 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2016-07-24 22:00:26 |
Launchpad Janitor |
bind9 (Ubuntu): status |
New |
Confirmed |
|
| 2016-07-27 08:45:18 |
dino99 |
tags |
amd64 apport-bug patch wily |
amd64 apport-bug patch wily xenial yakkety |
|
| 2016-07-27 23:03:02 |
Alberto Salvia Novella |
bind9 (Ubuntu): importance |
Undecided |
High |
|
| 2016-08-02 15:38:09 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Server Team |
| 2016-08-02 15:38:14 |
Robie Basak |
tags |
amd64 apport-bug patch wily xenial yakkety |
amd64 apport-bug patch server-next wily xenial yakkety |
|
| 2016-08-17 18:28:39 |
peteradleralberti |
bug |
|
|
added subscriber peteradleralberti |
| 2016-09-19 21:45:24 |
Jason B. Alonso |
bug |
|
|
added subscriber Jason B. Alonso |
| 2016-10-05 23:36:59 |
Nish Aravamudan |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-10-05 23:36:59 |
Nish Aravamudan |
bug task added |
|
bind9 (Ubuntu Xenial) |
|
| 2016-10-05 23:43:47 |
Nish Aravamudan |
bind9 (Ubuntu): assignee |
|
Nish Aravamudan (nacc) |
|
| 2016-10-05 23:43:51 |
Nish Aravamudan |
bind9 (Ubuntu Xenial): assignee |
|
Nish Aravamudan (nacc) |
|
| 2016-10-05 23:43:53 |
Nish Aravamudan |
bind9 (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-10-06 18:43:43 |
Nish Aravamudan |
bind9 (Ubuntu): status |
Confirmed |
In Progress |
|
| 2016-10-06 18:43:48 |
Nish Aravamudan |
bind9 (Ubuntu Xenial): status |
New |
In Progress |
|
| 2016-11-10 00:49:40 |
Nish Aravamudan |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-11-10 00:49:40 |
Nish Aravamudan |
bug task added |
|
bind9 (Ubuntu Yakkety) |
|
| 2016-11-10 00:49:50 |
Nish Aravamudan |
bind9 (Ubuntu Yakkety): status |
New |
In Progress |
|
| 2016-11-10 00:49:54 |
Nish Aravamudan |
bind9 (Ubuntu Yakkety): importance |
Undecided |
High |
|
| 2016-11-10 00:49:55 |
Nish Aravamudan |
bind9 (Ubuntu Yakkety): assignee |
|
Nish Aravamudan (nacc) |
|
| 2016-11-14 19:23:26 |
Nish Aravamudan |
description |
I enabled the bind9-resolvconf service and restarted my system, because I want to use the named running on localhost as my nameserver.
Even after the restart, however, the nameservers in /etc/resolv.conf (actually /var/run/resolvconf/resolv.conf) were still the ones provided by DHCP. This, despite the fact that the logs claim that bind9-resolvconf ran successfully during boot.
I tried manually running "sudo systemctl start bind9-resolv.conf", and again, the logs claim it ran, but /etc/resolv.conf was unmodified.
Finally, I manually ran "sudo /bin/sh -c 'echo nameserver 127.0.0.1 | /sbin/resolvconf -a lo.named'", i.e., the command listed in /lib/systemd/system/bind9-resolv.conf.service, and _that_ successfully updated /etc/resolv.conf.
After doing that, interestingly, "sudo systemctl stop bind9-resolv.conf" _also_ doesn't change /etc/resolv.conf, i.e., it still retains the 127.0.0.1 line which I added by running the resolvconf command manually.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: bind9 1:9.9.5.dfsg-11ubuntu1.2
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
Uname: Linux 4.2.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jan 20 08:03:35 2016
InstallationDate: Installed on 2016-01-16 (4 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
bind9utils 1:9.9.5.dfsg-11ubuntu1.2
apparmor 2.10-0ubuntu6
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.bind.named.conf: [modified]
modified.conffile..etc.bind.named.conf.local: [modified]
mtime.conffile..etc.bind.named.conf: 2016-01-16T19:01:39.827033
mtime.conffile..etc.bind.named.conf.local: 2016-01-16T21:13:51.991632 |
[Impact]
* If using the bind9-resolvconf service to have the local named managed resolv.conf, the service exits after running starting, and the system resolv.conf ends up reverting to the default content.
* The user is effectively prevented from using bind9-resolvconf to manage their local resolv.conf.
* The issue is that the bind9-resolvconf service needs to detected as still running even after the /etc/resolv.conf modification occurs. As per Debian Bug 744304: "RemainAfterExit tells systemd that a service should be considered running even after it exited. Currently, systemd thinks the service went inactive after the ExecStart command exits, and then immediately calls the ExecStop command, thus removing 127.0.0.1 from resolvconf."
[Test Case]
* Install bind9-resolvconf with a local bind9 configuration. Start the bind9-resolvconf service and the prior content of /etc/resolv.conf will remain even if it differs from bind9's configuration.
[Regression Potential]
* I believe the regression potential to be very low for this change. The bind9-resolvconf service currently does not work as expected. Users may have made manual changes locally, as suggested in this bug, but those seem to generally not be permanent solutions and should not collide with the change to the service.
---
I enabled the bind9-resolvconf service and restarted my system, because I want to use the named running on localhost as my nameserver.
Even after the restart, however, the nameservers in /etc/resolv.conf (actually /var/run/resolvconf/resolv.conf) were still the ones provided by DHCP. This, despite the fact that the logs claim that bind9-resolvconf ran successfully during boot.
I tried manually running "sudo systemctl start bind9-resolv.conf", and again, the logs claim it ran, but /etc/resolv.conf was unmodified.
Finally, I manually ran "sudo /bin/sh -c 'echo nameserver 127.0.0.1 | /sbin/resolvconf -a lo.named'", i.e., the command listed in /lib/systemd/system/bind9-resolv.conf.service, and _that_ successfully updated /etc/resolv.conf.
After doing that, interestingly, "sudo systemctl stop bind9-resolv.conf" _also_ doesn't change /etc/resolv.conf, i.e., it still retains the 127.0.0.1 line which I added by running the resolvconf command manually.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: bind9 1:9.9.5.dfsg-11ubuntu1.2
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
Uname: Linux 4.2.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jan 20 08:03:35 2016
InstallationDate: Installed on 2016-01-16 (4 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
bind9utils 1:9.9.5.dfsg-11ubuntu1.2
apparmor 2.10-0ubuntu6
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.bind.named.conf: [modified]
modified.conffile..etc.bind.named.conf.local: [modified]
mtime.conffile..etc.bind.named.conf: 2016-01-16T19:01:39.827033
mtime.conffile..etc.bind.named.conf.local: 2016-01-16T21:13:51.991632 |
|
| 2016-11-15 16:33:36 |
Nish Aravamudan |
bind9 (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2016-11-15 16:33:40 |
Nish Aravamudan |
bind9 (Ubuntu Yakkety): status |
In Progress |
Fix Committed |
|
| 2016-11-15 16:33:45 |
Nish Aravamudan |
bind9 (Ubuntu Yakkety): status |
Fix Committed |
In Progress |
|
| 2016-11-15 18:47:09 |
Launchpad Janitor |
bind9 (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2016-11-17 23:19:57 |
Brian Murray |
bind9 (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-11-17 23:19:59 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-11-17 23:20:03 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2016-11-17 23:20:12 |
Brian Murray |
tags |
amd64 apport-bug patch server-next wily xenial yakkety |
amd64 apport-bug patch server-next verification-needed wily xenial yakkety |
|
| 2016-11-18 14:39:05 |
Jonathan Kamens |
tags |
amd64 apport-bug patch server-next verification-needed wily xenial yakkety |
amd64 apport-bug patch server-next verification-done wily xenial yakkety |
|
| 2016-11-28 23:29:59 |
Launchpad Janitor |
bind9 (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-11-28 23:30:13 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-03-22 18:40:54 |
Nish Aravamudan |
bind9 (Ubuntu Xenial): assignee |
Nish Aravamudan (nacc) |
|
|
| 2017-03-22 18:41:01 |
Nish Aravamudan |
bind9 (Ubuntu): assignee |
Nish Aravamudan (nacc) |
|
|
| 2017-03-23 18:16:37 |
Brian Murray |
bind9 (Ubuntu Yakkety): status |
In Progress |
Fix Committed |
|
| 2017-03-23 18:16:45 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-03-23 18:16:58 |
Brian Murray |
tags |
amd64 apport-bug patch server-next verification-done wily xenial yakkety |
amd64 apport-bug patch server-next wily xenial yakkety |
|
| 2017-03-23 18:16:59 |
Brian Murray |
tags |
amd64 apport-bug patch server-next wily xenial yakkety |
amd64 apport-bug patch server-next verification-needed wily xenial yakkety |
|
| 2017-04-09 21:59:42 |
Jonathan Kamens |
tags |
amd64 apport-bug patch server-next verification-needed wily xenial yakkety |
amd64 apport-bug patch server-next verification-done wily xenial yakkety |
|
| 2017-04-12 12:12:11 |
Launchpad Janitor |
bind9 (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-06-30 17:02:48 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/326619 |
|
| 2017-06-30 17:03:59 |
Andreas Hasenack |
merge proposal unlinked |
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/326619 |
|
|
| 2017-07-05 17:37:15 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/326619 |
|
| 2017-07-10 18:09:17 |
Launchpad Janitor |
merge proposal unlinked |
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/326619 |
|
|
| 2017-08-24 21:30:26 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/329548 |
|
| 2017-08-24 22:28:57 |
Andreas Hasenack |
merge proposal unlinked |
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/329548 |
|
|
| 2017-10-23 11:17:14 |
Bug Watch Updater |
bind9 (Debian): status |
New |
Fix Released |
|
| 2018-07-11 15:01:56 |
Bug Watch Updater |
bind9 (Debian): status |
Fix Released |
New |
|
| 2021-02-25 04:01:59 |
Bug Watch Updater |
bind9 (Debian): status |
New |
Fix Released |
|
