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 confirmed that "systemctl restart
bind9-resolvconf" (see, no period this time!) is ineffective.
** Changed in: bind9 (Ubuntu)
Status: Incomplete => New
--
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/1536181
Title:
bind9-resolvconf service doesn't work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1536181/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
