bind9-resolvconf service doesn't work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Debian) |
Fix Released
|
Unknown
|
|||
bind9 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned | ||
Yakkety |
Fix Released
|
High
|
Nish Aravamudan |
Bug Description
[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/
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/
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.
ProcVersionSign
Uname: Linux 4.2.0-25-generic x86_64
NonfreeKernelMo
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)
RelatedPackageV
bind9utils 1:9.9.5.
apparmor 2.10-0ubuntu6
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
modified.
mtime.conffile.
mtime.conffile.
Changed in bind9 (Debian): | |
status: | Unknown → New |
Changed in bind9 (Ubuntu): | |
importance: | Undecided → High |
tags: | added: server-next |
Changed in bind9 (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in bind9 (Ubuntu Xenial): | |
status: | New → In Progress |
description: | updated |
Changed in bind9 (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in bind9 (Ubuntu Yakkety): | |
status: | In Progress → Fix Committed |
status: | Fix Committed → In Progress |
Changed in bind9 (Ubuntu Xenial): | |
assignee: | Nish Aravamudan (nacc) → nobody |
Changed in bind9 (Ubuntu): | |
assignee: | Nish Aravamudan (nacc) → nobody |
Changed in bind9 (Debian): | |
status: | New → Fix Released |
Changed in bind9 (Debian): | |
status: | Fix Released → New |
Changed in bind9 (Debian): | |
status: | New → Fix Released |
The service is called "bind9-resolvconf" but you said you ran "sudo systemctl start bind9-resolv.conf" and "sudo systemctl stop bind9-resolv.conf". Look carefully at the spelling.