Can you reproduce this on saucy or trusty?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1247148
Title:
rndc addzone isn't working. fix available
To manage notifications about this
This will not work because $OPTIONS is passed to named , while I have
altered arguements of start-stop-daemon
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1247148
Title:
rndc
** Changed in: bind9 (Ubuntu)
Status: New = Confirmed
** Changed in: bind9 (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1247148
snippet of /etc/apparmor.d/usr.sbin.named
# /etc/bind should be read-only for bind
# /var/lib/bind is for dynamically updated zone (and journal) files.
# /var/cache/bind is for slave/stub data, since we're not the origin of it.
# See /usr/share/doc/bind9/README.Debian.gz
/etc/bind/** r,
Charles,
I don't have Apparmor on this server. Yes, after changing init script from
-d /etc/bind
to
-d /var/lib/bind
Bind is still working, dynamic zones are created and served. It seems NZF files
can only be created in Bind's Currently Working Directory.
--
You received this bug notification
Perhaps a better approach would be to modify /etc/default/bind9.
$ cat /etc/default/bind9
# run resolvconf?
RESOLVCONF=no
# startup options for the server
OPTIONS=-u bind
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in
