Error: named restart failed /
Error: named restart failed /
Hi guys, hope u having a wonderful week. Yesterday i tried to make a new user and new domaing for my server and a weird error started popping up "Error: named restart failed", Tried to see the status of the service and this is the output of it.
[root@srv ~]# systemctl status named.service
● 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 Wed 2020-02-26 15:51:51 -03; 6min ago
Process: 3900 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)
Feb 26 15:51:51 srv.xy-sites.com bash[3900]: zone mueble.club/IN: loaded serial 2020021203
Feb 26 15:51:51 srv.xy-sites.com bash[3900]: zone mondbookings.com/IN: loaded serial 2020021203
Feb 26 15:51:51 srv.xy-sites.com bash[3900]: zone srv.xy-sites.com/IN: loaded serial 2020022501
Feb 26 15:51:51 srv.xy-sites.com bash[3900]: zone xy-sites.com/IN: NS 'srv.xy-sites.com' has no address records (A or AAAA)
Feb 26 15:51:51 srv.xy-sites.com bash[3900]: zone xy-sites.com/IN: not loaded due to errors.
Feb 26 15:51:51 srv.xy-sites.com bash[3900]: _default/xy-sites.com/IN: bad zone
Feb 26 15:51:51 srv.xy-sites.com systemd[1]: named.service: control process exited, code=exited status=1
Feb 26 15:51:51 srv.xy-sites.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Feb 26 15:51:51 srv.xy-sites.com systemd[1]: Unit named.service entered failed state.
Feb 26 15:51:51 srv.xy-sites.com systemd[1]: named.service failed.
I don't understand where's the problem, any advice?
[root@srv ~]# systemctl status named.service
● 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 Wed 2020-02-26 15:51:51 -03; 6min ago
Process: 3900 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)
Feb 26 15:51:51 srv.xy-sites.com bash[3900]: zone mueble.club/IN: loaded serial 2020021203
Feb 26 15:51:51 srv.xy-sites.com bash[3900]: zone mondbookings.com/IN: loaded serial 2020021203
Feb 26 15:51:51 srv.xy-sites.com bash[3900]: zone srv.xy-sites.com/IN: loaded serial 2020022501
Feb 26 15:51:51 srv.xy-sites.com bash[3900]: zone xy-sites.com/IN: NS 'srv.xy-sites.com' has no address records (A or AAAA)
Feb 26 15:51:51 srv.xy-sites.com bash[3900]: zone xy-sites.com/IN: not loaded due to errors.
Feb 26 15:51:51 srv.xy-sites.com bash[3900]: _default/xy-sites.com/IN: bad zone
Feb 26 15:51:51 srv.xy-sites.com systemd[1]: named.service: control process exited, code=exited status=1
Feb 26 15:51:51 srv.xy-sites.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Feb 26 15:51:51 srv.xy-sites.com systemd[1]: Unit named.service entered failed state.
Feb 26 15:51:51 srv.xy-sites.com systemd[1]: named.service failed.
I don't understand where's the problem, any advice?
-
thetechiepanda
- Posts: 2
- Joined: Sat Dec 11, 2021 6:41 pm
- Os: CentOS 6x
- Web: apache + nginx
Re: Error: named restart failed /
Did you manage to fix? I am having similar issue.
Re: Error: named restart failed /
You will need to fix the file manually.
The log reports that there are errors in zone xy-sites.com.
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 zone xy-sites.com.
Unfortunately VestaCP version 1.0 still has many bugs and I think the best solution would be for you to downgrade the vesta packages.