Hi Selva,
Thank you very much for your bug report.
This bug looks like it's caused by bind9
Setting up bind9 (1:9.7.0.dfsg.P1-1ubuntu0.5) ...
#
* Starting domain name service... bind9
...fail!
invoke-rc.d: initscript bind9, action "start" failed.
The only reasons why bind9 wouldn't start are
a) Misconfiguration of directory permissions
b) Misconfiguration of named.conf
Neither of this are caused by packaging, but I'd recommend you to start
reading the logs and see which configuration line is guilty for this, if
you need further help you can try other support options like going to
the irc channel #ubuntu-server on Freenode or joining the ubuntu-server
mailing list.
** Changed in: bind9 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015390
Title:
package bind9 1:9.7.0.dfsg.P1-1ubuntu0.5 failed to install/upgrade:
subprocess installed post-installation script returned error exit
status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1015390/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
