DNS restart failed

Community Support DNS
1

Hi,

Since last 2 weeks I’m receiving all days an email with the following message:

bind9 restart failed
"/usr/local/hestia/bin/v-restart-dns: line 31: /usr/sbin/named-checkconf: No such file or directory"

But when I enter to the server, bind9 is running, but if I launch “v-restart-dns” command I get:

root@server:/usr/local/hestia/bin# v-restart-dns 
ln: failed to create symbolic link '/sbin/named-checkconf': File exists
Error: bind9 restart failed'

I dont know exactly what is happen, and if it is important. Anyone knows how to solve this?

I am running HestiaCP 1.8.11 in Ubuntu 20.04.

Thanks in advance

2

Hi @saxico,

Take a look to this post:

You just need to edit this file /usr/local/hestia/bin/v-restart-dns and replace this line:

ln -s "$(which named-checkconf)" /sbin/named-checkconf

by this:

ln -s "$(which named-checkconf)" /usr/sbin/named-checkconf
2 Likes
3

Thanks a lot :slight_smile:

1 Like
4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.