9.2.4rc2

7 files changed, 295 insertions, 293 deletions

diff --git a/win32utils/BuildAll.bat b/win32utils/BuildAll.bat
index cd2235a1..bd5e5282 100644
--- a/win32utils/BuildAll.bat
+++ b/win32utils/BuildAll.bat
@@ -1,19 +1,19 @@
 echo off

 rem

-rem  Copyright (C) 2001  Internet Software Consortium.

-rem 

-rem  Permission to use, copy, modify, and distribute this software for any

-rem  purpose with or without fee is hereby granted, provided that the above

-rem  copyright notice and this permission notice appear in all copies.

-rem 

-rem  THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM

-rem  DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL

-rem  IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL

-rem  INTERNET SOFTWARE CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT,

-rem  INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING

-rem  FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,

-rem  NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION

-rem  WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

+rem Copyright (C) 2004  Internet Systems Consortium, Inc. ("ISC")

+rem Copyright (C) 2001,2003  Internet Software Consortium.

+rem

+rem Permission to use, copy, modify, and distribute this software for any

+rem purpose with or without fee is hereby granted, provided that the above

+rem copyright notice and this permission notice appear in all copies.

+rem

+rem THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH

+rem REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY

+rem AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,

+rem INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM

+rem LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE

+rem OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR

+rem PERFORMANCE OF THIS SOFTWARE.

 

 rem BuildAll.bat

 rem This script sets up the files necessary ready to build BIND 9

diff --git a/win32utils/BuildSetup.bat b/win32utils/BuildSetup.bat
index fca90b8f..6057c428 100644
--- a/win32utils/BuildSetup.bat
+++ b/win32utils/BuildSetup.bat
@@ -1,19 +1,19 @@
 echo off

 rem

-rem  Copyright (C) 2000, 2001  Internet Software Consortium.

-rem 

-rem  Permission to use, copy, modify, and distribute this software for any

-rem  purpose with or without fee is hereby granted, provided that the above

-rem  copyright notice and this permission notice appear in all copies.

-rem 

-rem  THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM

-rem  DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL

-rem  IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL

-rem  INTERNET SOFTWARE CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT,

-rem  INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING

-rem  FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,

-rem  NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION

-rem  WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

+rem Copyright (C) 2004  Internet Systems Consortium, Inc. ("ISC")

+rem Copyright (C) 2001-2003  Internet Software Consortium.

+rem

+rem Permission to use, copy, modify, and distribute this software for any

+rem purpose with or without fee is hereby granted, provided that the above

+rem copyright notice and this permission notice appear in all copies.

+rem

+rem THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH

+rem REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY

+rem AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,

+rem INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM

+rem LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE

+rem OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR

+rem PERFORMANCE OF THIS SOFTWARE.

 

 rem BuildSetup.bat

 rem This script sets up the files necessary ready to build BIND 9.

diff --git a/win32utils/dnsheadergen.bat b/win32utils/dnsheadergen.bat
index 64da64aa..83f6268e 100644
--- a/win32utils/dnsheadergen.bat
+++ b/win32utils/dnsheadergen.bat
@@ -1,19 +1,19 @@
 echo off

 rem

-rem  Copyright (C) 2000, 2001  Internet Software Consortium.

-rem 

-rem  Permission to use, copy, modify, and distribute this software for any

-rem  purpose with or without fee is hereby granted, provided that the above

-rem  copyright notice and this permission notice appear in all copies.

-rem 

-rem  THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM

-rem  DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL

-rem  IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL

-rem  INTERNET SOFTWARE CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT,

-rem  INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING

-rem  FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,

-rem  NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION

-rem  WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

+rem Copyright (C) 2004  Internet Systems Consortium, Inc. ("ISC")

+rem Copyright (C) 2001,2003  Internet Software Consortium.

+rem

+rem Permission to use, copy, modify, and distribute this software for any

+rem purpose with or without fee is hereby granted, provided that the above

+rem copyright notice and this permission notice appear in all copies.

+rem

+rem THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH

+rem REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY

+rem AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,

+rem INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM

+rem LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE

+rem OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR

+rem PERFORMANCE OF THIS SOFTWARE.

 

 cd ..\lib\dns

 cd win32

diff --git a/win32utils/makedefs.pl b/win32utils/makedefs.pl
index 723e8b90..49334a57 100644
--- a/win32utils/makedefs.pl
+++ b/win32utils/makedefs.pl
@@ -1,21 +1,21 @@
 #!/usr/bin/perl
 #
+# Copyright (C) 2004  Internet Systems Consortium, Inc. ("ISC")
 # Copyright (C) 2001  Internet Software Consortium.
 #
 # Permission to use, copy, modify, and distribute this software for any
 # purpose with or without fee is hereby granted, provided that the above
 # copyright notice and this permission notice appear in all copies.
 #
-# THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM
-# DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL
-# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
-# INTERNET SOFTWARE CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT,
-# INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
-# FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
-# NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
-# WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-
-# $Id: makedefs.pl,v 1.5 2001/07/31 00:03:19 gson Exp $
+# THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
+# REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
+# AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
+# INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
+# LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
+# OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
+# PERFORMANCE OF THIS SOFTWARE.
+
+# $Id: makedefs.pl,v 1.5.2.1 2004/03/09 06:12:48 marka Exp $
 
 # makedefs.pl
 # This script goes through all of the lib header files and creates a .def file
diff --git a/win32utils/makeversion.pl b/win32utils/makeversion.pl
index 7be62a2b..6464c4da 100644
--- a/win32utils/makeversion.pl
+++ b/win32utils/makeversion.pl
@@ -1,21 +1,21 @@
 #!/usr/bin/perl
 #
+# Copyright (C) 2004  Internet Systems Consortium, Inc. ("ISC")
 # Copyright (C) 2001  Internet Software Consortium.
 #
 # Permission to use, copy, modify, and distribute this software for any
 # purpose with or without fee is hereby granted, provided that the above
 # copyright notice and this permission notice appear in all copies.
 #
-# THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM
-# DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL
-# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
-# INTERNET SOFTWARE CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT,
-# INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
-# FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
-# NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
-# WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-
-# $Id: makeversion.pl,v 1.4 2001/07/27 17:25:23 gson Exp $ 
+# THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
+# REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
+# AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
+# INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
+# LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
+# OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
+# PERFORMANCE OF THIS SOFTWARE.
+
+# $Id: makeversion.pl,v 1.4.2.1 2004/03/09 06:12:48 marka Exp $ 
 
 # This script takes the version information from the version file located
 # at the root of the source tree and the api files in each library directory
diff --git a/win32utils/readme1st.txt b/win32utils/readme1st.txt
index 5f73399d..ca552d68 100644
--- a/win32utils/readme1st.txt
+++ b/win32utils/readme1st.txt
@@ -1,120 +1,121 @@
-Copyright (C) 2001, 2003  Internet Software Consortium.

-See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.

-

-$Id: readme1st.txt,v 1.7.2.5 2003/08/06 02:43:28 marka Exp $

-

-	   Release of BIND 9.2.3rc1 for Window NT/2000

-

-This is a maintenance release of BIND 9.2 for Window NT/2000.  Only

-IPv4 stacks are supported on the box running this version of BIND.

-IPv6 stacks will be supported in a future release.

-  

-	Kit Installation Information

-

-If you have previously installed BIND 8 or BIND 4 on the system that

-you wish to install this kit, you MUST use the BIND 8 or BIND 4 installer

-to uninstall the previous kit.  For BIND 8.2.x, you can use the

-BINDInstall that comes with the BIND 8 kit to uninstall it. The BIND 9

-installer will NOT uninstall the BIND 8 binaries.  That will be fixed

-in a future release.

-

-Unpack the kit into any convenient directory and run the BINDInstall

-program.  This will install the named and associated programs into

-the correct directories and set up the required registry keys.

-

-	Controlling BIND

-

-Windows NT/2000 uses the same rndc program as is used on Unix

-systems.  The rndc.conf file must be configured for your system in

-order to work. You will need to generate a key for this. To do this

-use the rndc-confgen program. The program will be installed in the

-same directory as named: dns/bin/.  From the DOS prompt, use the

-command this way:

-

-rndc-confgen -a

-

-which will create a rndc.key file in the dns/etc directory. This will

-allow you to run rndc without an explicit rndc.conf file or key and

-control entry in named.conf file. See section 3.4.1.2 of the ARM for

-details of this. An rndc.conf can also be generated by running:

-

-rndc-confgen > rndc.conf

-

-which will create the rndc.conf file in the current directory, but not

-copy it to the dns/etc directory where it needs to reside. If you create

-rndc.conf this way you will need to copy the same key statement into

-named.conf.

-

-The additions look like the following:

-

-key "rndc-key" { algorithm hmac-md5; secret "xxxxxxxxx=="; };

-

-controls {

-	inet 127.0.0.1 port 953 allow { localhost; } keys { "rndc-key"; };

-};

-

-Note that the value of the secret must come from the key generated

-above for rndc and must be the same key value for both. Details of

-this may be found in section 3.4.1.2 of the ARM. If you have rndc

-on a Unix box you can use it to control BIND on the NT/W2K box as

-well as using the Windows version of rndc to control a BIND 9

-daemon on a Unix box. However you must have key statements valid for

-the servers you wish to control, specifically the IP address and key

-in both named.conf and rndc.conf. Again see section 3.4.1.2 of the

-ARM for details.

-

-In addition BIND is installed as a win32 system service, can be

-started and stopped in the same way as any other service and

-automatically starts whenever the system is booted. Signals are

-not supported and are in fact ignored.

-

-Note: Unlike most Windows applications, named does not, change its

-working directory when started as a service.  If you wish to use

-relative files in named.conf you will need to specify a working

-directory.

-

-	Documentation

-

-This kit includes Documentation in HTML format.  The documentation is not

-copied during the installation process so you should move it to any convenient

-location for later reference. Of particular importance is the BIND 9

-Administrator's Reference Manual (Bv9ARM*.html) which provides detailed

-information on BIND 9. In addition, there are HTML pages for each of the

-BIND 9 applications.

-

-	DNS Tools

-

-The following tools have been built for Windows NT: dig, nslookup, host,

-nsupdate, rndc, rndc-confgen, named-checkconf, named-checkzone, dnssec-keygen,

-dnssec-makekeyset, dnssec-signkey, dnssec-signzone. The tools will NOT run on

-Win9x, only WinNT and Win2000. The latter tools are for use with DNSSEC. All

-tools are installed in the dns/bin directory.

-

-IMPORTANT NOTE ON USING THE TOOLS:

-If you wish to use nsupdate on a win32 platform to do dynamic updates

-to a zone you MUST create a resolv.conf in the System32\Drivers\etc

-directory containing a list of nameserver addresses to use to find

-the nameserver authoritative for the zone. The format of this file is:

-

-nameserver 1.2.3.4

-nameserver 5.6.7.8

-

-Replace the IP addresses with your real addresses.  127.0.0.1 is a valid

-address if you are running a nameserver on the localhost. 

-

-In addition, if you use dig, host or nslookup, you will need this

-file on the system where you are running these tools unless you have

-BIND running on that system.

-

-This will be fixed in a future release.

-

-Messages are logged to the Application log in the EventViewer.

-

-	Problems

-

-Please report all problems to bind9-bugs@isc.org and not to me. All

-other questions should go to the bind-users@isc.org mailing list or the

-comp.protocol.dns.bind news group.

-

-	Danny Mayer

-

+Copyright (C) 2004  Internet Systems Consortium, Inc. ("ISC")
+Copyright (C) 2001, 2003  Internet Software Consortium.
+See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
+
+$Id: readme1st.txt,v 1.7.2.7 2004/03/09 06:12:48 marka Exp $
+
+	   Release of BIND 9.2 for Window NT/2000
+
+This is a maintenance release of BIND 9.2 for Window NT/2000.  Only
+IPv4 stacks are supported on the box running this version of BIND.
+IPv6 stacks will be supported in a future release.
+  
+	Kit Installation Information
+
+If you have previously installed BIND 8 or BIND 4 on the system that
+you wish to install this kit, you MUST use the BIND 8 or BIND 4 installer
+to uninstall the previous kit.  For BIND 8.2.x, you can use the
+BINDInstall that comes with the BIND 8 kit to uninstall it. The BIND 9
+installer will NOT uninstall the BIND 8 binaries.  That will be fixed
+in a future release.
+
+Unpack the kit into any convenient directory and run the BINDInstall
+program.  This will install the named and associated programs into
+the correct directories and set up the required registry keys.
+
+	Controlling BIND
+
+Windows NT/2000 uses the same rndc program as is used on Unix
+systems.  The rndc.conf file must be configured for your system in
+order to work. You will need to generate a key for this. To do this
+use the rndc-confgen program. The program will be installed in the
+same directory as named: dns/bin/.  From the DOS prompt, use the
+command this way:
+
+rndc-confgen -a
+
+which will create a rndc.key file in the dns/etc directory. This will
+allow you to run rndc without an explicit rndc.conf file or key and
+control entry in named.conf file. See section 3.4.1.2 of the ARM for
+details of this. An rndc.conf can also be generated by running:
+
+rndc-confgen > rndc.conf
+
+which will create the rndc.conf file in the current directory, but not
+copy it to the dns/etc directory where it needs to reside. If you create
+rndc.conf this way you will need to copy the same key statement into
+named.conf.
+
+The additions look like the following:
+
+key "rndc-key" { algorithm hmac-md5; secret "xxxxxxxxx=="; };
+
+controls {
+	inet 127.0.0.1 port 953 allow { localhost; } keys { "rndc-key"; };
+};
+
+Note that the value of the secret must come from the key generated
+above for rndc and must be the same key value for both. Details of
+this may be found in section 3.4.1.2 of the ARM. If you have rndc
+on a Unix box you can use it to control BIND on the NT/W2K box as
+well as using the Windows version of rndc to control a BIND 9
+daemon on a Unix box. However you must have key statements valid for
+the servers you wish to control, specifically the IP address and key
+in both named.conf and rndc.conf. Again see section 3.4.1.2 of the
+ARM for details.
+
+In addition BIND is installed as a win32 system service, can be
+started and stopped in the same way as any other service and
+automatically starts whenever the system is booted. Signals are
+not supported and are in fact ignored.
+
+Note: Unlike most Windows applications, named does not, change its
+working directory when started as a service.  If you wish to use
+relative files in named.conf you will need to specify a working
+directory.
+
+	Documentation
+
+This kit includes Documentation in HTML format.  The documentation is not
+copied during the installation process so you should move it to any convenient
+location for later reference. Of particular importance is the BIND 9
+Administrator's Reference Manual (Bv9ARM*.html) which provides detailed
+information on BIND 9. In addition, there are HTML pages for each of the
+BIND 9 applications.
+
+	DNS Tools
+
+The following tools have been built for Windows NT: dig, nslookup, host,
+nsupdate, rndc, rndc-confgen, named-checkconf, named-checkzone, dnssec-keygen,
+dnssec-makekeyset, dnssec-signkey, dnssec-signzone. The tools will NOT run on
+Win9x, only WinNT and Win2000. The latter tools are for use with DNSSEC. All
+tools are installed in the dns/bin directory.
+
+IMPORTANT NOTE ON USING THE TOOLS:
+If you wish to use nsupdate on a win32 platform to do dynamic updates
+to a zone you MUST create a resolv.conf in the System32\Drivers\etc
+directory containing a list of nameserver addresses to use to find
+the nameserver authoritative for the zone. The format of this file is:
+
+nameserver 1.2.3.4
+nameserver 5.6.7.8
+
+Replace the IP addresses with your real addresses.  127.0.0.1 is a valid
+address if you are running a nameserver on the localhost. 
+
+In addition, if you use dig, host or nslookup, you will need this
+file on the system where you are running these tools unless you have
+BIND running on that system.
+
+This will be fixed in a future release.
+
+Messages are logged to the Application log in the EventViewer.
+
+	Problems
+
+Please report all problems to bind9-bugs@isc.org and not to me. All
+other questions should go to the bind-users@isc.org mailing list or the
+comp.protocol.dns.bind news group.
+
+	Danny Mayer
+
diff --git a/win32utils/win32-build.txt b/win32utils/win32-build.txt
index 30ef3b98..c895fc15 100644
--- a/win32utils/win32-build.txt
+++ b/win32utils/win32-build.txt
@@ -1,111 +1,112 @@
-Copyright (C) 2001  Internet Software Consortium.

-See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.

-

-$Id: win32-build.txt,v 1.5.2.1 2003/05/16 05:46:03 marka Exp $

-

-       BIND 9.2.0 Beta for Win32 Source Build Instructions.  28-Jul-2001

-

-Building BIND 9.2 on Windows NT/2000 has two prerequisites:

-1) You need to install Perl for Windows NT/2000. ActiveState

-(http://www.activestate.com/) is the one most people install and use;

-2) OpenSSL (http://www.openssl.org) needs to be downloaded and built

-on the system on which you are building BIND.

-

-The instructions assume a Visual C++ 6.0 compiler with Visual Studio and

-Visual Studio Service Pack 3 or later. It may build and work with earlier

-versions but it has not been tested. The binaries may be built and run on

-any of the following platforms: NT 4.0 Workstation (SP3 or later), NT 4.0

-Server (SP3 or later), Windows 2000 Professional (SP1 or later),

-Windows 2000 Server or any kind (SP1 or later). It should run on the

-to-be-released Windows XP platforms of various flavors. It will NOT build

-or run on Windows 95, Windows 98, etc. platforms.

-

-Step 1: Download and Build OpenSSL

-

-Download and untar the OpenSSL sources from http://www.openssl.org/.

-if you have place the BIND sources in /BIND9 you should place the

-OpenSSL sources in /OpenSSL-0.9.6b. If you place the sources anywhere

-else you will have to edit the libdns.dsp or libdns.mak files to point

-the include directories and the link library location to the correct

-places as well as move the DLL to the BUILD/Release subdirectory.

-

-Note: Building OpenSSL also requires that you install Perl as it uses

-it during its build process. Follow the instructions for NT given

-in the INSTALL.W32 file to build the kit. This will produce libeay32.lib

-and libeay32.dll in the out32dll subdirectory. 

-

-

-Step 2 Building BIND

-

-From the command prompt cd to the win32utils under the BIND root.

-Execute the BuildAll.bat file. This will do the following:

-1) copy config.h.win32 to config.h in the root.

-2) create the versions.h file in the root.

-3) Build the gen application in the lib/dns directory.

-4) Run the gen application and build the required lib/dns header

-   files.

-5) Create the Build/Release subdirectory under the root of the BIND

-   source tree which will hold the binaries being built.

-6) Build the libraries, named, application tools like dig, rndc

-   dnssec tools, installer, checkconf and checkzones programs,

-   BIND 9 Installer.

-7) Copies the release notes and the OpenSSL DLL to the BUILD/Release

-   directory.

-8) Copies the BIND 9 ARM HTML files and the application HTML files

-   to the Build\Release area.

-

-If you wish to use Visual Studio for building, you can just run the

-BuildSetup.bat file which will create all the necessary files and you

-can then use the BINDBuild.dsw to open the workspace for all of the

-libraries and applications. These files reside in the same win32utils

-directory as this file.

-

-The following files are built:

-

-libisc.dll

-libdns.dll

-libisccc.dll

-libisccfg.dll

-liblwres.dll

-named.exe

-bindevt.dll 

-BINDInstall.exe

-

-rndc.exe

-dig.exe

-host.exe

-nslookup.exe

-nsupdate.exe

-

-named-checkconf.exe

-named-checkzone.exe

-

-dnssec-keygen.exe

-dnssec-makekeyset.exe

-dnssec-signkey.exe

-dnssec-signzone.exe

-

-You should end up with 20 binaries in the bind9/Build/Release

-directory. The Install instructions Readme1st.txt from win32utils

-and libeay32.dll from the openssl/out32dll/ directory are also copied

-into the Build area. In addition you should have 22 HTML files.

-

-The set of files in the directory bind9/Build/Release form the

-installation kit which can then be zipped and distributed to any

-suitable Windows NT 4.0 or Windows 2000 platform.

-

-Installation is accomplished by running the BINDInstall program. All DLL's

-are copied to the system32 area and all applications (including BINDInstall

-which may be necessary for uninstalling BIND 9) to the dns/bin directory.

-If BIND 8 has previously been installed on the system it must be uninstalled

-first by running it's own BINDInstall program.  The BIND 9 installer does

-not yet do this.

-

-All bugs found, whether in the process of building the application or

-running BIND or the tools should be reported to the bind9 bugs email

-account at bind9-bugs@isc.org.

-

-	Danny Mayer

-	danny.mayer@nominum.com

-

-

+Copyright (C) 2004  Internet Systems Consortium, Inc. ("ISC")
+Copyright (C) 2001, 2003  Internet Software Consortium.
+See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
+
+$Id: win32-build.txt,v 1.5.2.2 2004/03/09 06:12:49 marka Exp $
+
+       BIND 9.2.0 Beta for Win32 Source Build Instructions.  28-Jul-2001
+
+Building BIND 9.2 on Windows NT/2000 has two prerequisites:
+1) You need to install Perl for Windows NT/2000. ActiveState
+(http://www.activestate.com/) is the one most people install and use;
+2) OpenSSL (http://www.openssl.org) needs to be downloaded and built
+on the system on which you are building BIND.
+
+The instructions assume a Visual C++ 6.0 compiler with Visual Studio and
+Visual Studio Service Pack 3 or later. It may build and work with earlier
+versions but it has not been tested. The binaries may be built and run on
+any of the following platforms: NT 4.0 Workstation (SP3 or later), NT 4.0
+Server (SP3 or later), Windows 2000 Professional (SP1 or later),
+Windows 2000 Server or any kind (SP1 or later). It should run on the
+to-be-released Windows XP platforms of various flavors. It will NOT build
+or run on Windows 95, Windows 98, etc. platforms.
+
+Step 1: Download and Build OpenSSL
+
+Download and untar the OpenSSL sources from http://www.openssl.org/.
+if you have place the BIND sources in /BIND9 you should place the
+OpenSSL sources in /OpenSSL-0.9.6b. If you place the sources anywhere
+else you will have to edit the libdns.dsp or libdns.mak files to point
+the include directories and the link library location to the correct
+places as well as move the DLL to the BUILD/Release subdirectory.
+
+Note: Building OpenSSL also requires that you install Perl as it uses
+it during its build process. Follow the instructions for NT given
+in the INSTALL.W32 file to build the kit. This will produce libeay32.lib
+and libeay32.dll in the out32dll subdirectory. 
+
+
+Step 2 Building BIND
+
+From the command prompt cd to the win32utils under the BIND root.
+Execute the BuildAll.bat file. This will do the following:
+1) copy config.h.win32 to config.h in the root.
+2) create the versions.h file in the root.
+3) Build the gen application in the lib/dns directory.
+4) Run the gen application and build the required lib/dns header
+   files.
+5) Create the Build/Release subdirectory under the root of the BIND
+   source tree which will hold the binaries being built.
+6) Build the libraries, named, application tools like dig, rndc
+   dnssec tools, installer, checkconf and checkzones programs,
+   BIND 9 Installer.
+7) Copies the release notes and the OpenSSL DLL to the BUILD/Release
+   directory.
+8) Copies the BIND 9 ARM HTML files and the application HTML files
+   to the Build\Release area.
+
+If you wish to use Visual Studio for building, you can just run the
+BuildSetup.bat file which will create all the necessary files and you
+can then use the BINDBuild.dsw to open the workspace for all of the
+libraries and applications. These files reside in the same win32utils
+directory as this file.
+
+The following files are built:
+
+libisc.dll
+libdns.dll
+libisccc.dll
+libisccfg.dll
+liblwres.dll
+named.exe
+bindevt.dll 
+BINDInstall.exe
+
+rndc.exe
+dig.exe
+host.exe
+nslookup.exe
+nsupdate.exe
+
+named-checkconf.exe
+named-checkzone.exe
+
+dnssec-keygen.exe
+dnssec-makekeyset.exe
+dnssec-signkey.exe
+dnssec-signzone.exe
+
+You should end up with 20 binaries in the bind9/Build/Release
+directory. The Install instructions Readme1st.txt from win32utils
+and libeay32.dll from the openssl/out32dll/ directory are also copied
+into the Build area. In addition you should have 22 HTML files.
+
+The set of files in the directory bind9/Build/Release form the
+installation kit which can then be zipped and distributed to any
+suitable Windows NT 4.0 or Windows 2000 platform.
+
+Installation is accomplished by running the BINDInstall program. All DLL's
+are copied to the system32 area and all applications (including BINDInstall
+which may be necessary for uninstalling BIND 9) to the dns/bin directory.
+If BIND 8 has previously been installed on the system it must be uninstalled
+first by running it's own BINDInstall program.  The BIND 9 installer does
+not yet do this.
+
+All bugs found, whether in the process of building the application or
+running BIND or the tools should be reported to the bind9 bugs email
+account at bind9-bugs@isc.org.
+
+	Danny Mayer
+	danny.mayer@nominum.com
+
+