• 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 Can not change DNS server-wide settings

klowet

Basic Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
18.0.57 #1
Hi

In DNS Settings > Server-wide settings, I want to add the notify yes; also-notify { ... } records. But when I save these changes, I get this error:

Error: dnsmng failed: dnsmng: Could not start named-checkconf
System error 2: No such file or directory

The log from panel.log:
[2023-11-29 08:02:25.555] 3786:6566e2018790c ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/dnsmng' '--test'] with exit code [1]
[2023-11-29 08:02:25.555] 3786:6566e2018790c ERR [panel] '/opt/psa/admin/bin/dnsmng' '--test' failed with code 1.

stdout:
dnsmng: Could not start named-checkconf
System error 2: No such file or directory


stderr:
dnsmng: Could not start named-checkconf
System error 2: No such file or directory

[2023-11-29 08:02:25.723] 3786:6566e2018790c ERR [panel.ui] dnsmng failed: dnsmng: Could not start named-checkconf<br />
System error 2: No such file or directory<br><a href='http://kb.plesk.com/plesk-error/sea...conf System+error+:+No+such+file+or+directory' target='_blank'>Search for related Knowledge Base articles</a>

It's a fresh Plesk installation on Debian 12.


Thanks
 
Hi @klowet !
I was able to reproduce the issue on Plesk 18.0.57.1+Debian12. At the same time, it does not appear on Debian11 and RHELbased OSes (like Alam8), so it looks like OS-specific. I'll try to dig into it and let you know.
 
Hello again!
The cause of the issue is that in Debian 12 part of the DNS utilities were moved to another directory. The current behavior was confirmed as a bug that is yet to be fixed. In the meantime, there is a simple workaround available:
1. Connect to the server via SSH.
2. Create a link to the checkconf file in the error message by running "ln -s /usr/{bin,sbin}/named-checkconf"
 
Back
Top