DNS Server (BIND) will not start

[kuhle]

I have a server running Centos5 and Plesk 8.6. Setting it up before migrating data from an old server onto it, and I have some test domains there.

Just created a vhost.conf file for a particular domain:
/var/www/vhosts/domain.com/conf/vhost.conf
in which I had only one line to turn on errors:

php_admin_flag display_errors On

then did

/usr/local/psa/admin/sbin/websrvmng -v -a

and then from Plesk CP went to restart Apache.

That was fine, but I noticed that DNS server not working. From Plesk CP, I get:

ERROR: PleskFatalException
Create ShortcutCreate Shortcut
Up LevelUp Level
Unable to make action: Unable to manage service by dnsmng: dnsmng: Service /etc/init.d/named failed to start

0: /usr/local/psa/admin/plib/common_func.php3:190
psaerror(string 'Unable to make action: Unable to manage service by dnsmng: dnsmng: Service /etc/init.d/named failed to start')
1: /usr/local/psa/admin/htdocs/server/restart_services.php:28

and from SSH I get:

[root@plesk2 ~]# /etc/init.d/named start
Locating /var/named/chroot//etc/named.conf failed:
[FAILED]
[root@plesk2 ~]# /etc/init.d/named restart
Stopping named: [ OK ]
Locating /var/named/chroot//etc/named.conf failed:
[FAILED]
[root@plesk2 ~]#

Can anyone help me out of this predicament?

 

[Vasilios G.D]

Help!

I have the exact same problem!

Can someone reply?!

Thanks

 

[Vasilios G.D]

I have the exact same problem! How did you solve it? Anyone can help on this?

Thanks

 

[Vasilios G.D]

Turns out the problem was cause because at some point the hard drive was out of space. This cause the configuration file to get damaged somehow even though it did not look that way. By disabling the DNS service for the particular domain that seemed to cause the Bind startup to fail and then enabling it again, the configuration was successfully rewritten and everything works fine now.