- Plesk for Windows
Note: This article has the reference to the issues with the fixes available:
- #PPPM-10403 "It is possible to add invalid address/prefix value to allow-transfer and crash ISC BIND (as PPP-41780)"
- #PPP-41780 "Plesk now prevents users from creating invalid DNS records that could cause the BIND service to crash."
ISC BIND is used as DNS server in Tools & Settings > Services Management
Going to Domains > example.com > DNS settings > Zone Transfers, there is a single IP address with a subnet mask, which is considered an incorrect syntax in ISC BIND. For example: 203.0.113.2/24
ISC BIND service cannot be started, by logging server via RDP in Services, it fails with the following error message:
CONFIG_TEXT: The process terminated unexpectedly. (Error code 1067) at Start service named
One of the following errors might be shown in Event Viewer > Windows Logs > Application:
CONFIG_TEXT: C:\Program Files (x86)\Parallels\Plesk\dns\etc\named.conf:835: '203.0.113.2/24': address/prefix length mismatch
CONFIG_TEXT: C:\Program Files (x86)\Parallels\Plesk\dns\etc\named.conf:835: expected IP match list element near ';'Click here to see how to apply filters in Event Viewer to find the error message
Configure filter as shown the image below:
Invalid IP address is added into Domains > example.com > DNS settings > Zone Transfers causing ISC Bind to crash.
The ability to add an invalid IP address is considered to be a bug with IDs #PPPM-10403 and #PPPM-10874, which are planned to be fixed in upcoming Plesk updates.
As a workaround:
Connect to the server via RDP
C:\> plesk db dump psa > psa.backup.sql
Fix the database values:
C:\> plesk db "update dns_recs set opt='' where type='AXFR' and val='203.0.113.2' and opt='24'"
* Where 203.0.113.2 is the IP address and 24 is the subnet shown in the error message from the symptoms section.
Propagate the changes to
%plesk_dir%dns\etc\named.confconfig file running
plesk repair dnscommand:
C:\> plesk repair dns -y