Resolved Can not change DNS server-wide settings

[klowet]

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='https://kb.plesk.com/plesk-error/se...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

 

[Yaroslav_T]

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.

 

[Yaroslav_T]

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"

 

[klowet]

Thanks @Yaroslav_T, that fix does work.