• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved DNS does not start anymore

H.W.B

Regular Pleskian
Hello,

After updating CentOS (Kernel etc) and a restart of plesk my Bind (DNS) would not start any more.
The log shows
named-checkconf[1754]: /etc/named.conf:5: open: /var/named/chroot/etc/own_specifications.conf: file not found
Failed to start Berkeley Internet Name Domain (DNS).

The strange thing is, that the file own_configuration.conf is in the directory and is filled with data (not empty).

Already try repair -r but that does not solve the problem.

Can someone help please??

Henk
 
Message log files shows:

Aug 30 12:24:04 plesk systemd: Starting Generate rndc key for BIND (DNS)...
Aug 30 12:24:04 plesk systemd: Started Generate rndc key for BIND (DNS).
Aug 30 12:24:04 plesk systemd: Starting Berkeley Internet Name Domain (DNS)...
Aug 30 12:24:04 plesk named-checkconf: /etc/named.conf:5: open: /var/named/chroot/etc/own_specifications.conf: file not found
Aug 30 12:24:04 plesk systemd: named-chroot.service: control process exited, code=exited status=1
Aug 30 12:24:04 plesk systemd: Failed to start Berkeley Internet Name Domain (DNS).
Aug 30 12:24:04 plesk systemd: Unit named-chroot.service entered failed state.
Aug 30 12:24:04 plesk systemd: named-chroot.service failed.
 
named.conf is a symbolic link on mine....
Maybe it got overwritten one time without noticing....
Because your DNS-server has stopped it is now forced to use the current /etc/named.conf
It may have rejected the config before, but kept running...

Try this first

Code:
ls -l /etc/named.conf

If it's not a symbolic link then try this:

Code:
mv /etc/named.conf /etc/named.conf.strange
ln -s /var/named/run-root/etc/named.conf /etc/named.conf
ls -l /etc/named.conf
/etc/init.d/named start
 
Hello,

It is a sym-link to /var/named/chroot/etc/named.conf
I do not have a dir run-root. Only chroot.

Thank you

Henk
 
We would like to know what happened....
It would also help someone who has a similar problem....
 
Back
Top