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.
Error: named restart failed
-
- Posts: 2
- Joined: Sat Dec 11, 2021 6:41 pm
- Os: CentOS 6x
- Web: apache + nginx
Error: named restart failed
Hi To All Members,
I am running a server on Centos 7 and has a VESTA CP installed on it.
Recently I did an update using yum update and now the named is not starting and on attempting restart it is giving Error: named restart failed
On running:
I got the below:
I have already tried to rebuild the DNS in VESTA CP->USERS but that has not helped.
I am pulling my hairs to figure our a solution. Any suggestions would be highly appreciated.
I am running a server on Centos 7 and has a VESTA CP installed on it.
Recently I did an update using yum update and now the named is not starting and on attempting restart it is giving Error: named restart failed
On running:
Code: Select all
sudo systemctl status named.service -l
Code: Select all
named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2021-12-12 01:32:49 UTC; 5min ago
Process: 24930 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE)
Main PID: 1079 (code=exited, status=0/SUCCESS)
Dec 12 01:32:49 dc-168e0f7e5238.thelavendersforlife.com bash[24930]: dns_rdata_fromtext: /home/admin/conf/dns/thelavendersforlife.com.db:16: near 'thelavendersforlife.com': bad dotted quad
Dec 12 01:32:49 dc-168e0f7e5238.thelavendersforlife.com bash[24930]: dns_rdata_fromtext: /home/admin/conf/dns/thelavendersforlife.com.db:23: near 'thelavendersforlife.com': bad dotted quad
Dec 12 01:32:49 dc-168e0f7e5238.thelavendersforlife.com bash[24930]: zone thelavendersforlife.com/IN: loading from master file /home/admin/conf/dns/thelavendersforlife.com.db failed: bad dotted quad
Dec 12 01:32:49 dc-168e0f7e5238.thelavendersforlife.com bash[24930]: zone thelavendersforlife.com/IN: not loaded due to errors.
Dec 12 01:32:49 dc-168e0f7e5238.thelavendersforlife.com bash[24930]: _default/thelavendersforlife.com/IN: bad dotted quad
Dec 12 01:32:49 dc-168e0f7e5238.thelavendersforlife.com bash[24930]: zone thetechiepanda.com/IN: loaded serial 2021121101
Dec 12 01:32:49 dc-168e0f7e5238.thelavendersforlife.com systemd[1]: named.service: control process exited, code=exited status=1
Dec 12 01:32:49 dc-168e0f7e5238.thelavendersforlife.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Dec 12 01:32:49 dc-168e0f7e5238.thelavendersforlife.com systemd[1]: Unit named.service entered failed state.
Dec 12 01:32:49 dc-168e0f7e5238.thelavendersforlife.com systemd[1]: named.service failed.
[root@dc-168e0f7e5238 centos]# /etc/bind/zones# named-checkzone thelavendersforlife.com
I am pulling my hairs to figure our a solution. Any suggestions would be highly appreciated.
Re: Error: named restart failed
You will need to fix the file /home/admin/conf/dns/thelavendersforlife.com.db manually.
The log reports that there are errors in lines 16 and 23 of file /home/admin/conf/dns/thelavendersforlife.com.db.
Unfortunately VestaCP version 1.0 still has many bugs and I think the best solution would be for you to downgrade the vesta packages.
The log reports that there are errors in lines 16 and 23 of file /home/admin/conf/dns/thelavendersforlife.com.db.
Unfortunately VestaCP version 1.0 still has many bugs and I think the best solution would be for you to downgrade the vesta packages.