I get "Error 1067" when starting named under Windows.
  • 10 Oct 2018
  • 1 Minute to read
  • Contributors
  • Dark
    Light
  • PDF

I get "Error 1067" when starting named under Windows.

  • Dark
    Light
  • PDF

This is the service manager saying that named exited.

Examine the Application log in the EventViewer to find out why.

Common causes are that you failed to create "named.conf" (usually "C:\windows\dns\etc\named.conf") or failed to specify the directory in named.conf.

options { Directory "C:\windows\dns\etc";};