ISC BIND cannot start ERROR 1067: The process terminated unexpectedly

Created:

2016-11-16 12:42:11 UTC

Modified:

2017-03-30 03:57:10 UTC

2

Was this article helpful?


Have more questions?

Submit a request

ISC BIND cannot start ERROR 1067: The process terminated unexpectedly

Symptoms

BIND service cannot start. Attempt to start ISC BIND from Services, produces the following error message:

ERROR 1067: The process terminated unexpectedly.

Cause

BIND DNS configuration file is not consistent.

Resolution

To resolve the issue please follow the steps bellow:

  1. Open the Event log
  2. Find the entry with the error:
    “C:\\\\Program Files (x86)\\\\Parallels\\\\Plesk\\\\dns\\\\etc\\\

    amed.conf:XXX: expected IP match list element near ';'”

where XXX – line number in "%plesk_dir%"\\dns\\etc\
amed.conf

  1. Open "%plesk_dir%"\\dns\\etc\
    amed.conf
  2. Find and remove the line XXX with a single symbol, " ; "
  3. Start BIND service via Windows Services:
    Services.msc
Have more questions? Submit a request
Please sign in to leave a comment.