Knowledge Base

ISC BIND service cannot be started on Windows: ERROR 1067: The process terminated unexpectedly

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:
```
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:
```
C:Program Files (x86)ParallelsPleskdnsetcnamed.conf:835: '203.0.113.2/24': address/prefix length mismatch
```
```
C:Program Files (x86)ParallelsPleskdnsetcnamed.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:

Product issues:

#PPPM-10874 “It is now possible to add only IP addresses (without a mask) in Domains > domain > DNS Settings > Zone Transfers.”

Fixed in:
- Plesk Obsidian 23 June 2020
#PPPM-10403 “Plesk now prevents users from creating invalid DNS records that could cause the BIND service to crash.”

Fixed in:
- Plesk Onyx 17.8 24 June 2019 (Windows)
- Plesk Obsidian 08 May 2019 (fixed as PPP-41780, Windows)

Please consider updating your server:

If update is not possible for some reason you may try the following

As a workaround:

Connect to the server via RDP
Start CMD as Administrator
Back up Plesk database:

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%dnsetcnamed.conf config file running plesk repair dns command:

C:> plesk repair dns -y