In message <2500b6c60809111121i422f0830g814d9a6c89245925@mail. gmail.com>, "Jame
s Burnie" writes:
> ...first time user of BIND...
> I am trying to install BIND 9.5.0-P2-W1 on a windows XP system. The "named"
> user is assigned with correct permissions and is able to login as a service.
> However, the ISC BIND service will not start. I checked the event viewer
> logs and they indicate that file named.conf is missing from
> windows\system32\dns\etc. Upon checking same directory, I discover that the
> bindinstall process did not populate any files there. If I create a blank
> "named.conf" file in that directory, I discover that I am then able to start
> the ISC BIND service successfully.
>
> My questions:
> 1. Should named.conf have been created as part of the bindinstall process?


No. We don't do this for unix either.

> 2. Are there any other files that should have been created in
> windows\system32\dns\etc as part of bindinstall?


No. named.conf, rndc.conf or rndc.key are all post install.
See readme.1st.

Note: BIND 9.5.0-P2-W2 is due out rsn to address the udp client
handler shutting down in BIND 9.5.0-P2-W1.

> 3. What do I need to do to get this working correctly?
>
> Thanks,
> James Burnie
>
>
>

--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org