From 00d5712510aa66b262594f8846d3666c0de2a204 Mon Sep 17 00:00:00 2001 From: "Internet Software Consortium, Inc" <@isc.org> Date: Tue, 1 Nov 2011 14:42:38 -0600 Subject: 9.8.1 --- win32utils/readme1st.txt | 318 ++++++++++++++++++++++----------------------- win32utils/win32-build.txt | 302 +++++++++++++++++++++--------------------- 2 files changed, 310 insertions(+), 310 deletions(-) (limited to 'win32utils') diff --git a/win32utils/readme1st.txt b/win32utils/readme1st.txt index 538c5bf2..1e401907 100644 --- a/win32utils/readme1st.txt +++ b/win32utils/readme1st.txt @@ -1,159 +1,159 @@ -Copyright (C) 2004, 2005, 2007-2009 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.24 2009-09-01 06:51:47 marka Exp $ - - Release of BIND 9.7 for Windows and later. - -This is a release of BIND 9.7 for Windows XP and later. - - Important Kit Installation Information - -As of release 9.3.0, BINDInstall requires that you install it under -a account with restricted privileges. The installer will prompt -you for an account name, the default is "named", and a password for -that account. It will also check for the existence of that account. -If it does not exist is will create it with only the privileges -required to run BIND. If the account does exist it will check that -it has only the one privilege required: "Log on as a service". If -it has too many privileges it will prompt you if you want to continue. - -With BIND running under an account name it is necessary for all -files and directories that BIND uses to have permissions set up for -the named account if the files are on an NTFS disk. BIND requires -that the account have read and write access to the directory for -the pid file, any files that are maintained either for slave zones -or for master zones supporting dynamic updates. The account will -also need read access to the named.conf and any other file that it -needs to read. - -"NT AUTHORITY\LocalService" is also an acceptable account. This -account is built into Windows and no password is required. Appropriate -file permissions will also need to be set for "NT AUTHORITY\LocalService" -similar to those that would have been required for the "named" account. - -It is important that on Windows the directory directive is used in -the options section to tell BIND where to find the files used in -named.conf (default %WINDOWS%\system32\dns\etc\named.conf). - -e.g. - options { - directory "C:\WINDOWS\system32\dns\etc"; - }; - -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. - -Messages are logged to the Application log in the EventViewer. - - Controlling BIND - -Windows 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 Windows 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 order to you rndc from a different system it is important to -ensure that the clocks are synchronized. The clocks must be kept -within 5 minutes of each other or the rndc commands will fail -authentication. Use NTP or other time synchronization software to -keep your clocks accurate. NTP can be found at http://www.ntp.org/. - -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 using the directory directive options. - - 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: dig, nslookup, -host, nsupdate, rndc, rndc-confgen, named-checkconf, named-checkzone, -dnssec-keygen, dnssec-signzone, dnssec-dsfromkey and dnssec-keyfromlabel. -The latter tools are for use with DNSSEC. All tools are installed -in the dns/bin directory. - -IMPORTANT NOTE ON USING THE TOOLS: - -It is no longer necessary to create a resolv.conf file on Windows -as the tools will look in the registry for the required nameserver -information. However if you wish to create a resolv.conf file as -follows it will use it in preference to the registry nameserver -entries. - -To create a resolv.conf you need to place it in the System32\Drivers\etc -directory and it needs to contain 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. - - 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 - mayer@ntp.isc.org - +Copyright (C) 2004, 2005, 2007-2009 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.24 2009-09-01 06:51:47 marka Exp $ + + Release of BIND 9.7 for Windows and later. + +This is a release of BIND 9.7 for Windows XP and later. + + Important Kit Installation Information + +As of release 9.3.0, BINDInstall requires that you install it under +a account with restricted privileges. The installer will prompt +you for an account name, the default is "named", and a password for +that account. It will also check for the existence of that account. +If it does not exist is will create it with only the privileges +required to run BIND. If the account does exist it will check that +it has only the one privilege required: "Log on as a service". If +it has too many privileges it will prompt you if you want to continue. + +With BIND running under an account name it is necessary for all +files and directories that BIND uses to have permissions set up for +the named account if the files are on an NTFS disk. BIND requires +that the account have read and write access to the directory for +the pid file, any files that are maintained either for slave zones +or for master zones supporting dynamic updates. The account will +also need read access to the named.conf and any other file that it +needs to read. + +"NT AUTHORITY\LocalService" is also an acceptable account. This +account is built into Windows and no password is required. Appropriate +file permissions will also need to be set for "NT AUTHORITY\LocalService" +similar to those that would have been required for the "named" account. + +It is important that on Windows the directory directive is used in +the options section to tell BIND where to find the files used in +named.conf (default %WINDOWS%\system32\dns\etc\named.conf). + +e.g. + options { + directory "C:\WINDOWS\system32\dns\etc"; + }; + +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. + +Messages are logged to the Application log in the EventViewer. + + Controlling BIND + +Windows 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 Windows 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 order to you rndc from a different system it is important to +ensure that the clocks are synchronized. The clocks must be kept +within 5 minutes of each other or the rndc commands will fail +authentication. Use NTP or other time synchronization software to +keep your clocks accurate. NTP can be found at http://www.ntp.org/. + +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 using the directory directive options. + + 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: dig, nslookup, +host, nsupdate, rndc, rndc-confgen, named-checkconf, named-checkzone, +dnssec-keygen, dnssec-signzone, dnssec-dsfromkey and dnssec-keyfromlabel. +The latter tools are for use with DNSSEC. All tools are installed +in the dns/bin directory. + +IMPORTANT NOTE ON USING THE TOOLS: + +It is no longer necessary to create a resolv.conf file on Windows +as the tools will look in the registry for the required nameserver +information. However if you wish to create a resolv.conf file as +follows it will use it in preference to the registry nameserver +entries. + +To create a resolv.conf you need to place it in the System32\Drivers\etc +directory and it needs to contain 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. + + 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 + mayer@ntp.isc.org + diff --git a/win32utils/win32-build.txt b/win32utils/win32-build.txt index 5eeaed5e..25f0c5a4 100644 --- a/win32utils/win32-build.txt +++ b/win32utils/win32-build.txt @@ -1,151 +1,151 @@ -Copyright (C) 2004, 2005, 2008, 2009 Internet Systems Consortium, Inc. ("ISC") -Copyright (C) 2001, 2002 Internet Software Consortium. -See COPYRIGHT in the source root or http://isc.org/copyright.html for terms. - -$Id: win32-build.txt,v 1.19 2009-11-06 03:14:10 each Exp $ - - BIND 9.7 for Win32 Source Build Instructions. 02-Jul-2009 - -Building BIND 9.7 on Windows XP/2003/2008 has the following prerequisites: - -1) You need to install Perl for Windows. ActivePerl -(http://www.activestate.com/) and Strawberry Perl -(http://www.strawberryperl.com) have both been tested and found -to work. - -2) OpenSSL (http://www.openssl.org) needs to be downloaded and built -on the system on which you are building BIND. - -3) If you wish to use the statistics channel, LibXML2 -(ftp://xmlsoft.org/libxml2) needs to be downloaded and built on -the system on which you are building BIND. (If you do not wish -to use the statistics channel, remove HAVE_LIBXML2 from config.h.win32.) - -4) If you want to build using Visual C++ 6.0, you'll need some extra -files that are to be found in the Platform SDK (which you will need -to install), namely: - -iphlpapi.h -iptypes.h -ipexport.h -iphlpapi.lib - -You'll also need an updated Iprtrmib.h - using the VC++6.0 one will -get you some compilation errors. You can just overwrite the old one if -you're not using it for any purposes, and maybe keep a backup of it. - -You can copy the header files under VC98\INCLUDE and the library file -under VC98\LIB. I think you can also put them in a separate directory -and add it to the include search list, but I don't know if that can be -made persistent. - -For building on VC++ 7.0 no extra files are required. - -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), Windows XP, Windows 2003 -Server. 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/. -Extract them at in the same directory in which you extracted the BIND9 -source: If BIND9 is in \build\bind-9.7.0, for instance, OpenSSL should be -in \build\openssl-0.9.8l (subject to version number changes). - -Note: Building OpenSSL requires that you install Perl as it uses -it during its build process. The following commands work as of -openssl-0.9.8l, but you should check the OpenSSL distribution -to see if the build instructions have changed: - - cd openssl-0.9.8l - perl Configure VC-WIN32 --prefix=c:/openssl - ms\do_masm - nmake /f ms\ntdll.mak - -If you wish to use PKCS #11 to control a cryptographic hardware service -module, please see bind9\README.pkcs11. You will need to apply the patch -in bind9\bin\pkcs11\openssl-0.9.8l-patch (this can be done using the Cygwin -'patch' utility) and add --pk11-libname and --pk11-flavor to the Configure -command above. - -Step 2: Download and build libxml2 - -Download and untar the libxml2 sources from ftp://xmlsoft.org/libxml2. -Extract them at in the same directory in which you extracted the BIND9 -source: If BIND9 is in \build\bind-9.7.0, for instance, libxml2 should -be in \build\libxml2-2.7.3 (subject to version number changes). - -Now build libxml2, and copy the resulting files into the include and lib -directories: - - cd libxml2-2.7.3\win32 - cscript configure.js compiler=msvc vcmanifest=yes static=yes debug=no iconv=no - nmake /f Makefile.msvc libxml - -Step 3: Building BIND - -You must build openssl and libxml2 first. - -From the command prompt cd to the win32utils directory under -the BIND9 root: - - cd bind-9.7.0\win32utils - -If you wish to use PKCS #11 to control a cryptographic hardware service -module, set the path to the PKCS #11 provider library: - - perl setpk11provider.pl - -If using VC++ 6.0, run the BuildAll.bat file: - - BuildAll - -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 the Visual Studio GUI for building, you can just -run the BuildSetup.bat file: - - BuildSetup - -This will create or find and copy into place several files which are -necessary for the build to proceed. It also locates and copies into place -the DLLs for OpenSSL and libxml2. - -Use BINDBuild.dsw (also located in the win32utils directory) to open the -workspace for all of the BIND9 libraries and applications. Select -"Build->Batch Build", click "Select All", then click "Build". - -After the build has completed, run the BuildPost.bat file: - - BuildPost - -...which does post-build processing. - -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. +Copyright (C) 2004, 2005, 2008, 2009 Internet Systems Consortium, Inc. ("ISC") +Copyright (C) 2001, 2002 Internet Software Consortium. +See COPYRIGHT in the source root or http://isc.org/copyright.html for terms. + +$Id: win32-build.txt,v 1.19 2009-11-06 03:14:10 each Exp $ + + BIND 9.7 for Win32 Source Build Instructions. 02-Jul-2009 + +Building BIND 9.7 on Windows XP/2003/2008 has the following prerequisites: + +1) You need to install Perl for Windows. ActivePerl +(http://www.activestate.com/) and Strawberry Perl +(http://www.strawberryperl.com) have both been tested and found +to work. + +2) OpenSSL (http://www.openssl.org) needs to be downloaded and built +on the system on which you are building BIND. + +3) If you wish to use the statistics channel, LibXML2 +(ftp://xmlsoft.org/libxml2) needs to be downloaded and built on +the system on which you are building BIND. (If you do not wish +to use the statistics channel, remove HAVE_LIBXML2 from config.h.win32.) + +4) If you want to build using Visual C++ 6.0, you'll need some extra +files that are to be found in the Platform SDK (which you will need +to install), namely: + +iphlpapi.h +iptypes.h +ipexport.h +iphlpapi.lib + +You'll also need an updated Iprtrmib.h - using the VC++6.0 one will +get you some compilation errors. You can just overwrite the old one if +you're not using it for any purposes, and maybe keep a backup of it. + +You can copy the header files under VC98\INCLUDE and the library file +under VC98\LIB. I think you can also put them in a separate directory +and add it to the include search list, but I don't know if that can be +made persistent. + +For building on VC++ 7.0 no extra files are required. + +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), Windows XP, Windows 2003 +Server. 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/. +Extract them at in the same directory in which you extracted the BIND9 +source: If BIND9 is in \build\bind-9.7.0, for instance, OpenSSL should be +in \build\openssl-0.9.8l (subject to version number changes). + +Note: Building OpenSSL requires that you install Perl as it uses +it during its build process. The following commands work as of +openssl-0.9.8l, but you should check the OpenSSL distribution +to see if the build instructions have changed: + + cd openssl-0.9.8l + perl Configure VC-WIN32 --prefix=c:/openssl + ms\do_masm + nmake /f ms\ntdll.mak + +If you wish to use PKCS #11 to control a cryptographic hardware service +module, please see bind9\README.pkcs11. You will need to apply the patch +in bind9\bin\pkcs11\openssl-0.9.8l-patch (this can be done using the Cygwin +'patch' utility) and add --pk11-libname and --pk11-flavor to the Configure +command above. + +Step 2: Download and build libxml2 + +Download and untar the libxml2 sources from ftp://xmlsoft.org/libxml2. +Extract them at in the same directory in which you extracted the BIND9 +source: If BIND9 is in \build\bind-9.7.0, for instance, libxml2 should +be in \build\libxml2-2.7.3 (subject to version number changes). + +Now build libxml2, and copy the resulting files into the include and lib +directories: + + cd libxml2-2.7.3\win32 + cscript configure.js compiler=msvc vcmanifest=yes static=yes debug=no iconv=no + nmake /f Makefile.msvc libxml + +Step 3: Building BIND + +You must build openssl and libxml2 first. + +From the command prompt cd to the win32utils directory under +the BIND9 root: + + cd bind-9.7.0\win32utils + +If you wish to use PKCS #11 to control a cryptographic hardware service +module, set the path to the PKCS #11 provider library: + + perl setpk11provider.pl + +If using VC++ 6.0, run the BuildAll.bat file: + + BuildAll + +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 the Visual Studio GUI for building, you can just +run the BuildSetup.bat file: + + BuildSetup + +This will create or find and copy into place several files which are +necessary for the build to proceed. It also locates and copies into place +the DLLs for OpenSSL and libxml2. + +Use BINDBuild.dsw (also located in the win32utils directory) to open the +workspace for all of the BIND9 libraries and applications. Select +"Build->Batch Build", click "Select All", then click "Build". + +After the build has completed, run the BuildPost.bat file: + + BuildPost + +...which does post-build processing. + +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. -- cgit v1.2.3