** Changed in: bind9 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf service doesn't work
To manage notifications about
** Changed in: bind9 (Debian)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf service doesn't work
To manage notifications about
** Changed in: bind9 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf service doesn't work
To manage notifications about
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/329548
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1536181
Title:
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/329548
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/329548
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/326619
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/326619
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/326619
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/326619
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/326619
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1536181
Title:
This bug was fixed in the package bind9 - 1:9.10.3.dfsg.P4-10.1ubuntu1.4
---
bind9 (1:9.10.3.dfsg.P4-10.1ubuntu1.4) yakkety; urgency=medium
* Add RemainAfterExit to bind9-resolvconf unit configuration file
(LP: #1536181).
-- Nishanth Aravamudan
bind9 1:9.10.3.dfsg.P4-10.1ubuntu1.4 seems to solve the problem.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
Hello Jonathan, or anyone else affected,
Accepted bind9 into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bind9/1:9.10.3.dfsg.P4-10.1ubuntu1.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new
** Changed in: bind9 (Ubuntu Xenial)
Assignee: Nish Aravamudan (nacc) => (unassigned)
** Changed in: bind9 (Ubuntu)
Assignee: Nish Aravamudan (nacc) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package bind9 - 1:9.10.3.dfsg.P4-8ubuntu1.3
---
bind9 (1:9.10.3.dfsg.P4-8ubuntu1.3) xenial; urgency=medium
* Add RemainAfterExit to bind9-resolvconf unit configuration file
(LP: #1536181).
-- Nishanth Aravamudan Tue,
Tested successfully:
Package: bind9
Version: 1:9.10.3.dfsg.P4-8ubuntu1.3
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Hello Jonathan, or anyone else affected,
Accepted bind9 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bind9/1:9.10.3.dfsg.P4-8ubuntu1.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
This bug was fixed in the package bind9 - 1:9.10.3.dfsg.P4-10.1ubuntu2
---
bind9 (1:9.10.3.dfsg.P4-10.1ubuntu2) zesty; urgency=medium
* Add RemainAfterExit to bind9-resolvconf unit configuration file
(LP: #1536181).
-- Nishanth Aravamudan Tue,
** Changed in: bind9 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf service doesn't work
To manage notifications
** Description changed:
+ [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
After removing my workaround (and confirming things were broken again),
I can confirm that the package in your PPA resolves the issue!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
@Jason, the PPA updates should be building now.
** Also affects: bind9 (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: bind9 (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: bind9 (Ubuntu Yakkety)
Importance: Undecided => High
** Changed in:
Oh, and to put the service override into effect:
sudo systemctl restart bind9-resolvconf.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf service doesn't work
While waiting for the PPA to update, I'll note for the record: I was
able to deploy a less invasive workaround by applying a service
override.
sudo systemctl edit bind9-resolvconf
In the provided editor (which is empty unless you have overrides
already), add:
[Service]
RemainAfterExit=yes
--
On Nov 6, 2016 14:29, "Jason B. Alonso" <1536...@bugs.launchpad.net> wrote:
>
> There have been security updates to bind9 since the builds in your PPA,
> which are conflicting with my ability to test it (please pardon me for
> being reluctant to fight apt to rewind the security update).
There have been security updates to bind9 since the builds in your PPA,
which are conflicting with my ability to test it (please pardon me for
being reluctant to fight apt to rewind the security update).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: bind9 (Ubuntu)
Status: Confirmed => In Progress
** Changed in: bind9 (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Hello, I have provided test builds with the updated systemd unit
configuration file at:
https://launchpad.net/~nacc/+archive/ubuntu/lp1536181.
Please test and report back!
** Also affects: bind9 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: bind9 (Ubuntu)
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf service doesn't work
To manage notifications about this bug go to:
** Changed in: bind9 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf service doesn't work
To manage notifications about this
Glancing at bind's bugs, i've opened that one to read it; and have
checked the yakkety status about it: so i've edited the file proposed in
#4 above, to looks like:
[Unit]
Description=local BIND via resolvconf
Documentation=man:named(8) man:resolvconf(8)
Requires=bind9.service
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bind9 (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/1536181
Title:
The attachment "bind9-resolvconf.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
** Changed in: bind9 (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536181
Title:
bind9-resolvconf service doesn't work
To manage notifications about this
The bug is still present in 16.04 xenial, bind9-1:9.10.3.dfsg.P4-8ubuntu1
package.
It is described well in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744304
The fix is to edit /lib/systemd/system/bind9-resolvconf.service and add
"RemainAfterExit=yes" at [Service] section. A patch is
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.
** Changed in: bind9 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
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.
** Changed in: bind9 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
So sue me, I accidentally typed bind9-resolv.conf instead of
bind9-resolvconf in my bug report. Obviously I would have noticed
systemctl tell me I typed an invalid service if I had actually typed
bind9-resolv.conf in the systemctl commands. I'm not an idiot. The bug
report is correct; I just
So sue me, I accidentally typed bind9-resolv.conf instead of
bind9-resolvconf in my bug report. Obviously I would have noticed
systemctl tell me I typed an invalid service if I had actually typed
bind9-resolv.conf in the systemctl commands. I'm not an idiot. The bug
report is correct; I just
40 matches
Mail list logo