ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

update

Browse Source
This commit is contained in:
Mark Andrews
2009-06-22 01:59:30 +00:00
parent c907893aaf
commit 420e099c2f
1 changed files with 57 additions and 63 deletions
Download Patch File Download Diff File Expand all files Collapse all files

120
win32utils/readme1st.txt
View File

@@ -2,35 +2,31 @@ Copyright (C) 2004, 2005, 2007, 2008 Internet Systems Consortium, Inc. ("ISC")
Copyright (C) 2001, 2003 Internet Software Consortium. Copyright (C) 2001, 2003 Internet Software Consortium.
See COPYRIGHT in the source root or http://isc.org/copyright.html for terms. See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
$Id: readme1st.txt,v 1.21 2009/06/22 01:47:00 each Exp $ $Id: readme1st.txt,v 1.22 2009/06/22 01:59:30 marka Exp $
Release of BIND 9.7 for Windows XP/2003/2008 Release of BIND 9.7 for Windows and later.
This is a release of BIND 9.7 for Windows XP/2003/2008. This is a release of BIND 9.7 for Windows XP and later.
Only IPv4 stacks are supported on the box running this version of BIND.
IPv6 stacks will be supported in a future release.
Important Kit Installation Information Important Kit Installation Information
As of release 9.3.0, BINDInstall requires that you install As of release 9.3.0, BINDInstall requires that you install it under
it under an account with restricted privileges. The installer an account with restricted privileges. The installer will prompt
will prompt you for an account name, the default is "named", and you for an account name, the default is "named", and a password for
a password for that account. It will also check for the existence that account. It will also check for the existence of that account.
of that account. If it does not exist is will create it with only If it does not exist is will create it with only the privileges
the privileges required to run BIND. If the account does exist it required to run BIND. If the account does exist it will check that
will check that it has only the one privilege required: it has only the one privilege required: "Log on as a service". If
"Log on as a service". If it has too many privileges it will prompt it has too many privileges it will prompt you if you want to continue.
you if you want to continue.
With BIND running under an account name it is necessary for all With BIND running under an account name it is necessary for all
files and directories that BIND uses to have permissions set up files and directories that BIND uses to have permissions set up for
for the named account if the files are on an NTFS disk. BIND requires 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 that the account have read and write access to the directory for
the pid file, any files that are maintained either for slave zones the pid file, any files that are maintained either for slave zones
or for master zones supporting dynamic updates. The account will or for master zones supporting dynamic updates. The account will
also need read access to the named.conf and any other file that also need read access to the named.conf and any other file that it
it needs to read. needs to read.
It is important that on Windows the directory directive is used in 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 the options section to tell BIND where to find the files used in
@@ -41,12 +37,12 @@ e.g.
directory "C:\WINDOWS\system32\dns\etc"; directory "C:\WINDOWS\system32\dns\etc";
}; };
If you have previously installed BIND 8 or BIND 4 on the system that If you have previously installed BIND 8 or BIND 4 on the system
you wish to install this kit, you MUST use the BIND 8 or BIND 4 installer that you wish to install this kit, you MUST use the BIND 8 or BIND
to uninstall the previous kit. For BIND 8.2.x, you can use the 4 installer to uninstall the previous kit. For BIND 8.2.x, you can
BINDInstall that comes with the BIND 8 kit to uninstall it. The BIND 9 use the BINDInstall that comes with the BIND 8 kit to uninstall it.
installer will NOT uninstall the BIND 8 binaries. That will be fixed The BIND 9 installer will NOT uninstall the BIND 8 binaries. That
in a future release. will be fixed in a future release.
Unpack the kit into any convenient directory and run the BINDInstall Unpack the kit into any convenient directory and run the BINDInstall
program. This will install the named and associated programs into program. This will install the named and associated programs into
@@ -56,12 +52,12 @@ Messages are logged to the Application log in the EventViewer.
Controlling BIND Controlling BIND
Windows NT/2000 uses the same rndc program as is used on Unix Windows uses the same rndc program as is used on Unix systems. The
systems. The rndc.conf file must be configured for your system in rndc.conf file must be configured for your system in order to work.
order to work. You will need to generate a key for this. To do this You will need to generate a key for this. To do this use the
use the rndc-confgen program. The program will be installed in the rndc-confgen program. The program will be installed in the same
same directory as named: dns/bin/. From the DOS prompt, use the directory as named: dns/bin/. From the DOS prompt, use the command
command this way: this way:
rndc-confgen -a rndc-confgen -a
@@ -72,10 +68,10 @@ details of this. An rndc.conf can also be generated by running:
rndc-confgen > rndc.conf rndc-confgen > rndc.conf
which will create the rndc.conf file in the current directory, but not which will create the rndc.conf file in the current directory, but
copy it to the dns/etc directory where it needs to reside. If you create not copy it to the dns/etc directory where it needs to reside. If
rndc.conf this way you will need to copy the same key statement into you create rndc.conf this way you will need to copy the same key
named.conf. statement into named.conf.
The additions look like the following: The additions look like the following:
@@ -88,24 +84,23 @@ controls {
Note that the value of the secret must come from the key generated 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 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 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 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 well as using the Windows version of rndc to control a BIND 9 daemon
daemon on a Unix box. However you must have key statements valid for on a Unix box. However you must have key statements valid for the
the servers you wish to control, specifically the IP address and key 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 in both named.conf and rndc.conf. Again see section 3.4.1.2 of the
ARM for details. ARM for details.
In order to you rndc from a different system it is important to In order to you rndc from a different system it is important to
ensure that the clocks are synchronized. The clocks must be kept ensure that the clocks are synchronized. The clocks must be kept
within 5 minutes of each other or the rndc commands will fail within 5 minutes of each other or the rndc commands will fail
authentication. Use NTP or other time synchronization software authentication. Use NTP or other time synchronization software to
to keep your clocks accurate. NTP can be found at keep your clocks accurate. NTP can be found at http://www.ntp.org/.
http://www.ntp.org/.
In addition BIND is installed as a win32 system service, can be In addition BIND is installed as a win32 system service, can be
started and stopped in the same way as any other service and started and stopped in the same way as any other service and
automatically starts whenever the system is booted. Signals are automatically starts whenever the system is booted. Signals are not
not supported and are in fact ignored. supported and are in fact ignored.
Note: Unlike most Windows applications, named does not, change its Note: Unlike most Windows applications, named does not, change its
working directory when started as a service. If you wish to use working directory when started as a service. If you wish to use
@@ -114,46 +109,45 @@ directory using the directory directive options.
Documentation Documentation
This kit includes Documentation in HTML format. The documentation is not This kit includes Documentation in HTML format. The documentation
copied during the installation process so you should move it to any convenient is not copied during the installation process so you should move
location for later reference. Of particular importance is the BIND 9 it to any convenient location for later reference. Of particular
Administrator's Reference Manual (Bv9ARM*.html) which provides detailed importance is the BIND 9 Administrator's Reference Manual (Bv9ARM*.html)
information on BIND 9. In addition, there are HTML pages for each of the which provides detailed information on BIND 9. In addition, there
BIND 9 applications. are HTML pages for each of the BIND 9 applications.
DNS Tools DNS Tools
The following tools have been built for Windows NT: dig, nslookup, The following tools have been built for Windows: dig, nslookup,
host, nsupdate, rndc, rndc-confgen, named-checkconf, named-checkzone, host, nsupdate, rndc, rndc-confgen, named-checkconf, named-checkzone,
dnssec-keygen, dnssec-signzone, dnssec-dsfromkey and dnssec-keyfromlabel. dnssec-keygen, dnssec-signzone, dnssec-dsfromkey and dnssec-keyfromlabel.
The tools will NOT run on Win9x, only WinNT and Win2000. The latter The latter tools are for use with DNSSEC. All tools are installed
tools are for use with DNSSEC. All tools are installed in the in the dns/bin directory.
dns/bin directory.
IMPORTANT NOTE ON USING THE TOOLS: IMPORTANT NOTE ON USING THE TOOLS:
It is no longer necessary to create a resolv.conf file on Windows as It is no longer necessary to create a resolv.conf file on Windows
the tools will look in the registry for the required nameserver as the tools will look in the registry for the required nameserver
information. However if you wish to create a resolv.conf file as information. However if you wish to create a resolv.conf file as
follows it will use it in preference to the registry nameserver follows it will use it in preference to the registry nameserver
entries. entries.
To create a resolv.conf you need to place it in the System32\Drivers\etc 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 directory and it needs to contain a list of nameserver addresses
use to find the nameserver authoritative for the zone. The format of to use to find the nameserver authoritative for the zone. The format
this file is: of this file is:
nameserver 1.2.3.4 nameserver 1.2.3.4
nameserver 5.6.7.8 nameserver 5.6.7.8
Replace the IP addresses with your real addresses. 127.0.0.1 is a valid Replace the IP addresses with your real addresses. 127.0.0.1 is a
address if you are running a nameserver on the localhost. valid address if you are running a nameserver on the localhost.
Problems Problems
Please report all problems to bind9-bugs@isc.org and not to me. All 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 other questions should go to the bind-users@isc.org mailing list
comp.protocol.dns.bind news group. or the comp.protocol.dns.bind news group.
Danny Mayer Danny Mayer
mayer@ntp.isc.org mayer@ntp.isc.org