Try to “sudo service bind9 stop” and “sudo service bind9 start” and see what happens
If this does not work, try to re-run the setup with “sudo mailinabox”.
Okay I did that and it gave me no errors or confirmations for restarting bind9, and rerunning the mailinabox ran fine without problems. It didn’t fix the problem. I am using impactvps.
Are you running Mail-in-a-Box on a clean and fresh Ubuntu 14.04 LTS Image?
Have you already tried to reset the whole machine, or creating a new one? Same bugs?
Can anybody reproduce this with ImpactVPS?
Type these in order in a root shell:
/etc/init.d/bind9.dpkg-dist start
update-rc.d bind9.dpkg-dist defaults
update-rc.d bind9.dpkg-dist enable
Bind9 should start working and would start upon reboots. The Ubuntu packaging probably made a mistake. They made the bind9 script an empty script that returns 0 for all cases, while leaving the real script at bind9.dpkg-dist.
I too have the same issue. Fixed it the way I mentioned above.
Hmm that get rid of one of the errors. I still seem to be getting. I don’t know if it really matters as I think i’m not using the DNS functionality of this. At least getting rid of the other errors allowed for me to see the other check marks. Should the firewall not be blocking for 953 because it seems to be blocking it?
Local DNS Control (bind9/rndc) is not running (port 953).
I think you may create problems in the future with that solution. The only reason I can think of that you have that file is during an update, or upgrade, of bind you were asked to accept the changes, (optionally compare a diff…) and you said No when you should have said yes.
Undo what you did and “mv /etc/init.d/bind9.dpkg-dist /etc/init.d/bind9”.