- 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)"
- Plesk Obsidian Release Candidate 1.0 04 June 2019
- #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;
Last octet of IP address with mask 24 is not 0 in Domains > example.com > DNS settings > Zone Transfers. For example: 203.0.113.2/24
ISC BIND service cannot be started by logging server via RDP in Services with the following message:
CONFIG_TEXT: The process terminated unexpectedly. (Error code 1067) at Start service named
On the server one of the errors like below can be found in** Event Viewer > Windows Logs > Application** command:
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 a proper filter in order 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. The ability to add invalid IP address is considered to be a bug with ID #PPPM-10403, which is planned to be fixed in product future updates.
As a workaround, until fix available use the following steps:
Connect to the server via RDP.
%plesk_dir%dns\etc\named.conffile with text editor and find for which zones incorrect mask is defined.
Log into Plesk.
Remove invalid IP address in Domains > example.com > DNS settings > Zone Transfers > 203.0.113.2/24.
Note: If it required, add IP address with last octet equal 0: 203.0.113.0/24;
Start ISC BIND service in Tools & Settings > Services Management.