bind9 RESOLVCONF does not work

Bug #1600210 reported by Alex Bligh on 2016-07-08
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
bind9 (Debian)
New
Unknown
bind9 (Ubuntu)
High
Robie Basak

Bug Description

Under 16.04, /etc/default/bind9 contains a RESOLVCONF option which appears not to work with systemd.

Under 14.04, setting RESOLVCONF="yes" in /etc/default/bind9 caused bind9 to be installed as a local resolver. This is done by lines 65-68 of the (16.04) /etc/init.d/bind9.

As far as I can tell, this is broken in 16.04 because systemd is used to start bind9 instead. This appears not to execute those lines (even '/etc/init.d/bind9 start' appears to be subverted judging by 'sh -x' output), and - again as far as I can tell - nothing is calling resolvconf instead. This appears to mean that bind9 no longer can install itself as a resolver, which is a pain.

There may be some systemd specific way of doing this, but I don't know what it is.

affects: nbd (Ubuntu) → bind9 (Ubuntu)
Alex Bligh (ubuntu-alex-org) wrote :

This may explain it:

root@shed2:~# systemctl list-units --all | egrep 'bind9|resolv'
  org.freedesktop.resolve1.busname loaded inactive dead Network Name Resolution Service Bus Name
  systemd-networkd-resolvconf-update.path loaded inactive dead Trigger resolvconf update for networkd DNS
  bind9-resolvconf.service loaded inactive dead local BIND via resolvconf
  bind9.service loaded active running BIND Domain Name Server
  resolvconf.service loaded active exited Nameserver information manager
  systemd-networkd-resolvconf-update.service loaded inactive dead Update resolvconf for networkd DNS
  systemd-resolved.service loaded inactive dead Network Name Resolution
root@shed2:~# systemctl list-unit-files --all | egrep 'bind9|resolv'
org.freedesktop.resolve1.busname static
systemd-networkd-resolvconf-update.path static
bind9-pkcs11.service disabled
bind9-resolvconf.service enabled
bind9.service enabled
dbus-org.freedesktop.resolve1.service disabled
resolvconf.service enabled
systemd-networkd-resolvconf-update.service static
systemd-resolved.service disabled

Note bind9-resolvconf.service is 'loaded inactive dead'

bind9-resolvconf.service was disabled, but even enabling it did not fix it.

Perhaps this is the cause:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744304

as RemainAfterExit=yes is not present in /lib/systemd/system/bind9-resolvconf.service

Alex Bligh (ubuntu-alex-org) wrote :

I can confirm that this can be fixed by carrying out the instructions here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744304#32

(i.e. adding a small systemd file)

then:

systemctl enable bind9-resolvconf.service

then restarting bind9.

I don't think it should really be this opaque ...

Robie Basak (racb) on 2016-07-08
Changed in bind9 (Ubuntu):
importance: Undecided → High
tags: added: server-next
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bind9 (Ubuntu):
status: New → Confirmed
Changed in bind9 (Debian):
status: Unknown → New
Robie Basak (racb) on 2016-09-19
Changed in bind9 (Ubuntu):
assignee: nobody → Robie Basak (racb)
Robie Basak (racb) on 2016-10-03
tags: removed: server-next
Changed in bind9 (Debian):
status: New → Fix Released
Andreas Hasenack (ahasenack) wrote :

The debian bug was closed as part of a mass-close, not due to an updated package.

Changed in bind9 (Debian):
status: Fix Released → New
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.