Vesta Control Panel - Forum

I'm running on a minimum install of ubuntu 14.04 64 bit, with the latest vesta. As far as I can tell, everything is working fine except my DNS server. On the server tab, named is greyed out, and won't start or restart when using the buttons there. I have setup everything for a nameserver as per the tutorial, but it doesn't resolve to anywhere because the named server won't start.

Can anyone point me in a good direction to get this solved??

can you show us your log files? Have you edit the config manually (not in vesta cp)?

tjebbeke wrote:can you show us your log files? Have you edit the config manually (not in vesta cp)?

The syslog has no entries for named or bind. I have not edited anything manually yet.

Can you rebuild the DNS of your users. (VestaCP (admin) -> USERS -> Toggle All -> rebuild DNS). Then start service again. If not work check config with If there is no output, the configuration is considered correct and you can safely restart or reload bind configuration file.

Thanks for the suggestions. I knew I saw a rebuild option somewhere but couldn't find it yesterday.

I did that, and tried to start the named server, no go. If I try to restart, it says action failed.

When I do a check on the path you mentioned on the named,conf, it comes back with file does not exist. My path is /etc/bind/named.conf. That takes me back to the prompt, so no errors, and I do see entries in there for my dns.

I also tried apt-install bind9 since it sure seems it didn't get installed, but it comes back with the latest version is already installed.

service bind9 status returns me to the prompt with no output, service named status comes back with: named: unrecognized service.

I've not solved the problem, but I have switched to Debian 7 minimal install, and all seems to be working, even after installing MariaDB over mysql. Must be some kind of ubuntu issue.....

Since it's a new install and I am still tinkering, I may try Debian 8 and see if that works too. Nice to be able to use the latest versions, helps to future proof yourself from headaches later....

Sorry to necro,

But has anyone else rub into this issue? I'm experiencing the exact same issue also with Ubuntu 14.04. Bind just wont start.

Well, this won't help much, but I switched to Webuzo panel because I wanted to go strictly nginx and ditch apache totally. What I've found with it, same issue. Under Ubuntu, bind says it starts, but shuts off immediately and won't stay running. Under centos, it worked fine.

I would have to say there is some underlying issue with bind and ubuntu and control panels. Perhaps like exim4 it puts it's files into a different directory in ubuntu than any other distro.

When you restart bind in console, everything ok or you see some errors?