We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Another DNS Named service issue
-
- Posts: 13
- Joined: Thu Jul 03, 2014 9:15 pm
Another DNS Named service issue
Hi
Have my new vps with ovh, and moved from another control panel to this one to test out. Got to say its miles ahead of the others i have used
First off my vps is 4gb ram, 3vcpu, CentOS 6 64bit running latest vesta cp installed today
Everything goes smoothly and following an initial reboot after cp install and set up, domains packages etc, all works great.
The OVH control panel shows DNS working and named shows as running in services in vesta.
I then vpn and upload to public_html my joomla zip and akeeba kickstart.php. The first time i did this earlier today kickstart installer worked first time and the site was accessible. However when i check the backend of ovh dns shows as disabled and vesta shows named service as stopped. Restart service fails. I done a fresh install of the vps and vesta and again all was good but after a server reboot (it would not access the kickstart.php the second time but did after reboot), the dns disabled and service stopped appears again, the site is however accesible from its web address.
I have seen some other threads but most switch to pm so havent been able to find the answer myself
Any help would be great
obviously replace website address with XXXXXXXX
Have my new vps with ovh, and moved from another control panel to this one to test out. Got to say its miles ahead of the others i have used
First off my vps is 4gb ram, 3vcpu, CentOS 6 64bit running latest vesta cp installed today
Everything goes smoothly and following an initial reboot after cp install and set up, domains packages etc, all works great.
The OVH control panel shows DNS working and named shows as running in services in vesta.
I then vpn and upload to public_html my joomla zip and akeeba kickstart.php. The first time i did this earlier today kickstart installer worked first time and the site was accessible. However when i check the backend of ovh dns shows as disabled and vesta shows named service as stopped. Restart service fails. I done a fresh install of the vps and vesta and again all was good but after a server reboot (it would not access the kickstart.php the second time but did after reboot), the dns disabled and service stopped appears again, the site is however accesible from its web address.
I have seen some other threads but most switch to pm so havent been able to find the answer myself
Any help would be great
Code: Select all
[root@vpsxxxxxx ~]# service named restart
Stopping named: [ OK ]
Starting named:
Error in named configuration:
zone xxxxxxx.co.uk/IN: loading from master file /home/admin/conf/dns/xxxxxxxxxx.db failed: file not found
zone xxxxxxx.co.uk/IN: not loaded due to errors.
_default/xxxxxxxxx/IN: file not found
[FAILED]
Code: Select all
[root@xxxxxxxxx ~]# service named configtest
zone xxxxxxxxxx.co.uk/IN: loading from master file /home/admin/conf/dns/xxxxxxxxx.co.uk.db failed: file not found
zone xxxxxxxxx.co.uk/IN: not loaded due to errors.
_default/xxxxxxxxx.co.uk/IN: file not found
Re: Another DNS Named service issue
Hi,
check this file xxxxxxxxx.co.uk.db on that path /home/admin/conf/dns/
Try to rebuild dns for your user in the vestacp
Code: Select all
zone xxxxxxxxxx.co.uk/IN: loading from master file /home/admin/conf/dns/xxxxxxxxx.co.uk.db failed: file not found
Try to rebuild dns for your user in the vestacp
-
- Posts: 13
- Joined: Thu Jul 03, 2014 9:15 pm
Re: Another DNS Named service issue
I shall try to rebuild and report back
Thanks for the prompt response
Thanks for the prompt response
-
- Posts: 13
- Joined: Thu Jul 03, 2014 9:15 pm
Re: Another DNS Named service issue
file located ok and seems intact, ill just try a few random things
thanks anyway
thanks anyway
Re: Another DNS Named service issue
thering1975, do you solved this problem ?
do you need my help?
do you need my help?
-
- Posts: 13
- Joined: Thu Jul 03, 2014 9:15 pm
Re: Another DNS Named service issue
hiya
nope no luck im afraid, however i did manage to uninstall the named package and reinstall it.
That half solves it, the service still disables itself but can be restarted via the cp without error, but will disable itself again at somepoint.
Im sure ill find a workaround somehow
nope no luck im afraid, however i did manage to uninstall the named package and reinstall it.
That half solves it, the service still disables itself but can be restarted via the cp without error, but will disable itself again at somepoint.
Im sure ill find a workaround somehow
-
- Posts: 13
- Joined: Thu Jul 03, 2014 9:15 pm
Re: Another DNS Named service issue
when vestacp stops services to do a backup named restarts a ok if the vps reboots then it wont restart at all yet i can still access all domains perfectly fine regardless
-
- Posts: 13
- Joined: Thu Jul 03, 2014 9:15 pm
Re: Another DNS Named service issue
Sussed it out
When installing vestacp i had updated the fresh install of centos before hand, and ignored Vesta error of bind already installed and used force mode.
On a new vps i installed os updates, then removed bind, Vesta then installed ok no warning and when i reboot server the service automatically restarts fine.
When installing vestacp i had updated the fresh install of centos before hand, and ignored Vesta error of bind already installed and used force mode.
On a new vps i installed os updates, then removed bind, Vesta then installed ok no warning and when i reboot server the service automatically restarts fine.
-
- Posts: 26
- Joined: Sat Jul 26, 2014 7:32 am
- Contact:
Re: Another DNS Named service issue
Does this mean we should not have bind on our CentOS image? Just named? I'm new to this and experiencing similar issues (or was previously) and would like to prevent problems by removing unnecessary packages.thering1975 wrote:When installing vestacp i had updated the fresh install of centos before hand, and ignored Vesta error of bind already installed and used force mode.
On a new vps i installed os updates, then removed bind, Vesta then installed ok no warning and when i reboot server the service automatically restarts fine.