the service named is currently down.

bg32am

Verified User
Joined
Mar 22, 2020
Messages
10
Hi,

I've just reboot my vps and all my websites are down now and i've this message:

This message has been automatically generated notifying you that the service named is currently down.

try to restart named but i can't , could you please help me .

Thanks
 
restart if from SSH console, check error message, check logs.
Code:
[root@ns ~]# systemctl status named -l

● named.service - Berkeley Internet Name Domain (DNS)

Loaded: loaded (/etc/systemd/system/named.service; enabled; vendor preset: disabled)

Active: failed (Result: exit-code) since Sun 2020-07-26 21:36:06 +0430; 9s ago

Process: 11158 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)
 
Last edited:
so replace broken NS records to default server's, or add appropriate A records, and modify serial number in zonefile, then restart named again.
looks like you pointed domain to own NSs (glue records) but forgot to create appropriate A-records for it.
 
I've got this message when try to fix zone :

Unable to save dns zone: named-checkzone returned:
 
Last edited:
chow me content of this .db file
or add A-records for NSs
ns1 14400 IN A xxx.xx.xx.xx
ns2 14400 IN A xxx.xx.xx.xx
 
I have the message too in the server:
The service 'named' on server xx.xx.xx is currently down
 
You might normally best start a new thread as your problem most likely has another cause.

Try using this command and see if there are errors:
named-checkconf
 
The named-checkconf , didn't show something
1674761499185.png
 
See post #2. Check logs.

Also try to restart named, and see if it throws errors and which errors:
service named restart
 
Oke there you go.

You masked them. But in the output you see that 3 domains do not have any A or AAA records. Most likely that is the cause.

See if those domains still exist, if yes, check their DNS and update as needed.
If not, remove them from DNS.
 
Also check if you have SELinux enabled, seems there is some authentication issue, might be caused by SELinux.
 
SElinux is not via systemctl.

Issue this command:
sestatus
then you can see if it's enabled or disabled. If it's disabled it's good.

How about the domains removal or fix I suggested?
 
Back
Top