Starting BIND on Windows 2000

[Lists at Curtis-M-Kularski.com]

:-) 

Status: BIND service is running.

Thank you so much, I had named.conf in the correct location, but it was
referring to the wrong location for everything else.  I have it now
pointing to d:\windows\system32\dns\var\named. 

I knew it had to be a simple mistake.  

--
Curtis M. Kularski
Curtis at Kularski.net
http://Curtis-M-Kularski.com
http://web.Curtis-Kularski.net 
 
Microsoft Associate Expert
http://Microsoft.com/WindowsXP/ExpertZone

Ask.com AnswerPoint Enthusiast (Bronze level)
http://AnswerPoint.Ask.com  
 


-----Original Message-----
From: Danny Mayer [mailto:mayer at gis.net] 
Sent: Saturday, August 11, 2001 11:53 PM
To: Lists at Curtis-M-Kularski.com; bind-users at isc.org
Subject: Re: Starting BIND on Windows 2000

At 04:55 PM 8/11/01, Lists at Curtis-M-Kularski.com wrote:
>I have created all of my db.(zone) files, and the named.conf file.  I
>have started the BIND Control Panel also.  I am following the
>instruction in the book "DNS and BIND 4th edition", but they don't seem
>to be working. I type "# /ect/named" in Startup Parameters, then I
click
>start, but after about 5 seconds, BIND stops. What should I use for the
>startup parameters?
>  
>I am using the Windows NT/2000 version of BIND 8.2.4.
>  

Nowhere in the documentation for BIND for NT were you told that you need
startup parameters.  BIND is installed as a system service and starts
automatically
when the system is started.  No parameters are needed.  You can start
and
stop BIND also from BINDCtrl and BINDCmd. You should read your
application
event log and see what errors it gets.  You need to set up named.conf in
dns/etc whereever you installed the software.  Error messages are sent
by
default to the application event log.  If you have startup errors then
you need
to look there.  Use Windows filespecs in named.conf (a forward slash '/'
is valid
for these paths).  Also take a look at http://bind8nt.meiway.com/ for
details.

         Danny