Commit bcd09706 authored by Danny Mayer's avatar Danny Mayer

Updated as release version and added rndc.key info

parent 8ff4edd1
Copyright (C) 2001 Internet Software Consortium.
See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
$Id: readme1st.txt,v 1.6 2001/08/02 07:03:58 mayer Exp $
$Id: readme1st.txt,v 1.7 2001/08/12 04:53:38 mayer Exp $
Beta Release of BIND 9.2.0 for Window NT/2000
Release of BIND 9.2.0 for Window NT/2000
Date: 20-Jul-2001.
Date: 10-Aug-2001.
This is a Beta Release of BIND 9.2.0 for Windows NT/2000. As such
it should not be installed on a production system or anywhere that is
considered critical for Internet access. The release has not been
thoroughly tested. While IPv6 addresses should work, there is no
support yet for a BIND server using an IPv6 stack. Only IPv4 stacks are
supported on the box running this version of BIND. IPv6 stacks will
be supported in a future release.
This is the first release of BIND 9.2.0 for Windows NT/2000. As such
it should be fully tested on a test system before installing on a
production system or anywhere that is considered critical for Internet
access. The release has not been thoroughly tested. While IPv6
addresses should work, there is no support yet for a BIND server using
an IPv6 stack. 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
......@@ -37,13 +37,21 @@ 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
An rndc.conf will be generated in the current directory but not copied to
the dns/etc directory where it needs to reside.
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.
In addition the named.conf file will need to be modified in order
to allow rndc to control named. The additions look like the following:
The additions look like the following:
key "rndc-key" { algorithm hmac-md5; secret "xxxxxxxxx=="; };
......@@ -52,14 +60,19 @@ controls {
};
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. 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.
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.
automatically starts whenever the system is booted. Signals are
not supported and are in fact ignored.
Documentation
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment