Do you have the same problem as stevetoza? If you cat /etc/init.d/bind9 does it look like the short snippet he posted earlier?
I think there’s something odd with your particular VPS setup. I would try another VPS provider.
1 Like
Thank you so much Josh and stevetoza.
You were both right!
service bind9.dpkg-dist start
Fixed it 
1 Like
@chainsaw glad you got it working 
@JoshData the VPS I’m hosting the mailinabox on is node that I look after, its the most up to date OpenVZ template for the uBuntu version. Wondering if the package for bind is slightly different.
I tried that but my system does not seem to have bind9.dpkg-dist start
I am having the same issue on a fresh install and like Luke, my system is reporting there is no bind9.dpkg-dist and that it is an unrecognized service. Any advice?
For those having this problem, please try
service bind9 restart
dig @localhost google.com
tail -100 /var/log/syslog
And paste the output.
Josh, Here are the results:
- Starting domain name service… bind9 [ OK ]
XXXXX@BOX:~$ dig @localhost google.com
; <<>> DiG 9.9.5-3-Ubuntu <<>> @localhost google.com
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13962
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 4, ADDITIONAL: 5
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 300 IN A 64.15.120.22
google.com. 300 IN A 64.15.120.27
google.com. 300 IN A 64.15.120.25
google.com. 300 IN A 64.15.120.23
google.com. 300 IN A 64.15.120.26
google.com. 300 IN A 64.15.120.20
google.com. 300 IN A 64.15.120.21
google.com. 300 IN A 64.15.120.24
;; AUTHORITY SECTION:
google.com. 172800 IN NS ns2.google.com.
google.com. 172800 IN NS ns3.google.com.
google.com. 172800 IN NS ns1.google.com.
google.com. 172800 IN NS ns4.google.com.
;; ADDITIONAL SECTION:
ns1.google.com. 172800 IN A 216.239.32.10
ns2.google.com. 172800 IN A 216.239.34.10
ns3.google.com. 172800 IN A 216.239.36.10
ns4.google.com. 172800 IN A 216.239.38.10
;; Query time: 404 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Dec 07 11:24:33 CST 2014
;; MSG SIZE rcvd: 303
XXXXX@BOX:~$ tail -100 /var/log/syslog
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 18.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 19.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 20.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 21.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 22.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 23.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 24.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 25.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 26.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 27.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 28.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 29.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 30.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 31.172.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 168.192.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 64.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 65.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 66.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 67.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 68.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 69.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 70.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 71.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 72.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 73.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 74.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 75.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 76.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 77.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 78.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 79.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 80.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 81.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 82.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 83.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 84.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 85.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 86.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 87.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 88.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 89.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 90.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 91.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 92.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 93.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 94.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 95.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 96.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 97.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 98.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 99.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 100.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 101.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 102.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 103.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 104.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 105.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 106.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 107.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 108.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 109.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 110.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 111.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 112.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 113.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 114.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 115.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 116.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 117.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 118.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 119.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 120.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 121.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 122.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 123.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 124.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 125.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 126.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 127.100.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 254.169.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: D.F.IP6.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 8.E.F.IP6.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 9.E.F.IP6.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: A.E.F.IP6.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: B.E.F.IP6.ARPA
Dec 7 11:24:22 BOX named[14675]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Dec 7 11:24:22 BOX named[14675]: command channel listening on 127.0.0.1#953
Dec 7 11:24:22 BOX named[14675]: managed-keys-zone: loaded serial 2
Dec 7 11:24:22 BOX named[14675]: zone 0.in-addr.arpa/IN: loaded serial 1
Dec 7 11:24:22 BOX named[14675]: zone 127.in-addr.arpa/IN: loaded serial 1
Dec 7 11:24:22 BOX named[14675]: zone 255.in-addr.arpa/IN: loaded serial 1
Dec 7 11:24:22 BOX named[14675]: zone localhost/IN: loaded serial 2
Dec 7 11:24:22 BOX named[14675]: all zones loaded
Dec 7 11:24:22 BOX named[14675]: running
XXXX@BOX:~$
I was able to resolve the problem tonight. I checked the open firewall ports in the server and added all the missing ones to our hardare based firewall/router. After doing so, the status page worked and I was able to use the WebDav, CalDav and CardDav services of OwnCloud.
Do you have a break down of what each port is for? I had to add 9 of them to the firewall with port forwarding. I would like to close any that aren’t necessary from the outside.
Glad you resolved the problem. The ports are:
22 SSH
25 SMTP (incoming mail)
53 DNS (tcp & udp)
80 HTTP (not strictly necessary)
443 HTTPS (webmail, the /admin control panel, static sites, ActiveSync)
587 SMTP (mail submission by box users)
993 IMAP (checking mail)
That’s seven. What were the other two you added? Maybe I missed something.
I had those setup already. I had to add:
10023
10025
10026
11211
10222
8952
8891
4190
They were all listening on the server.
None of these should be opened. All except 4190 are supposed to be bound to the loopback interface, meaning even without a firewall, connections from the outside should not be possible. That also means that firewall settings for these ports should have no effect. If the firewall settings have an effect, something else is wrong.
Here is what is on those ports:
4190 managesieve (user-provided mail filter scripting, binds on all interfaces, not sure about security)
8891 OpenDKIM
8952 nsd control
10023 Postgrey
10025 Spamassassin (spampd)
10026 Dovecot LDA
10222 Mail-in-a-Box management daemon
11211 Memcached, used by ownCloud
After an update the status page now generates Error Something went wrong, sorry. Thoughts on what to look at?
Please check /var/log/syslog. Let me know what you find.
When I hit Status check, the syslog shows a list of automatic empyt zone: XXXXXXX then it stops at
all zones loaded
running
Any insight would be helpful, still having the same problem. Even after a fresh install. I appreciate any help that anyone can provide. Thank you.
Sounds like it’s working fine but it’s taking too long and the http request is timing out (between nginx and the backend process).
You can also run management/status_checks.py from the command line to get similar output.
I will give that a try. Thanks!
Thank you for the status_checks.py tip, it revealed that it was calling ssh. Which was not installed. After installing the openssh-server all is well on the webadmin and command line!
Ahha, it’s trying to check that the sshd configuration is good. We’ll skip that if it’s not installed. Will be fixed in the next update. Thanks.
1 Like
The hosting provider I used did not have ubuntu-server images, only ubuntu-minimal, and I had the same issues.
What I had to do was install ubuntu-stantard package and then I could proceed normally.