bind as a service on windows "-c" option not working

Danny Mayer mayer at
Thu Dec 15 16:57:38 UTC 2011

On 12/15/2011 11:43 AM, Vbvbrj wrote:
> On 15.12.2011 15:39, Danny Mayer wrote:
> Thanks for answering.
>>> I want to keep all the files related to bind in one folder, not across
>>> the system folder. And keeping the named.conf in the system32 folder may
>>> be lost when the system is reinstalled and in a hurry the file is
>>> forgotten to be copied.
>> If you install the software in D:\bind9 then the binaries will be in
>> D:\bind9\bin and the config file named.conf will be in D:\bind9\etc. I
>> don't think you need anything else.
> The production I use for now is configured like you wrote^ all files
> under the install directory.
>> And the other thing is keeping the system's registry as simple and clean
>> as possible, by not using registry for start-up arguments and indicating
>> them in the command line for the service. This I managed to do for most
>> of the services I use.
>> If you do the above then you don't need to change anything in the
>> registry. That's the default behavior. If there are changes you want to
>> have added send a message to bind9-bugs.
> This is the problem. If the "InstallDir" key is deleted from the
> registry, the bind at start searches for the named.conf in the
> system32\etc folder and falls with an error. That's why I asked about
> the "-c" option that is not taken. If without that regystry key, the
> bind service will try to find a named.conf under the etc folder from
> where the executable resides - will be easier. For example PHP is
> searching for the ini file in systme32 folder, then in the executable
> folder, then in paths.

InstallDir is required in the registry for proper administration of BIND9.


More information about the bind-users mailing list