head	1.2;
access;
symbols
	RELENG_5_5_0_RELEASE:1.1.1.12.8.1
	RELENG_5_5:1.1.1.12.8.1.0.6
	RELENG_5_5_BP:1.1.1.12.8.1
	RELENG_5_4_0_RELEASE:1.1.1.12.8.1
	RELENG_5_4:1.1.1.12.8.1.0.4
	RELENG_5_4_BP:1.1.1.12.8.1
	RELENG_4_11_0_RELEASE:1.1.1.7.2.5
	RELENG_4_11:1.1.1.7.2.5.0.12
	RELENG_4_11_BP:1.1.1.7.2.5
	RELENG_5_3_0_RELEASE:1.1.1.12.8.1
	RELENG_5_3:1.1.1.12.8.1.0.2
	RELENG_5_3_BP:1.1.1.12.8.1
	RELENG_5:1.1.1.12.0.8
	RELENG_5_BP:1.1.1.12
	RELENG_4_10_0_RELEASE:1.1.1.7.2.5
	RELENG_4_10:1.1.1.7.2.5.0.10
	RELENG_4_10_BP:1.1.1.7.2.5
	RELENG_5_2_1_RELEASE:1.1.1.12
	RELENG_5_2_0_RELEASE:1.1.1.12
	RELENG_5_2:1.1.1.12.0.6
	RELENG_5_2_BP:1.1.1.12
	v8_3_7:1.1.1.12
	RELENG_4_9_0_RELEASE:1.1.1.7.2.5
	RELENG_4_9:1.1.1.7.2.5.0.8
	RELENG_4_9_BP:1.1.1.7.2.5
	v8_3_6:1.1.1.12
	RELENG_5_1_0_RELEASE:1.1.1.12
	RELENG_5_1:1.1.1.12.0.4
	RELENG_5_1_BP:1.1.1.12
	RELENG_4_8_0_RELEASE:1.1.1.7.2.5
	RELENG_4_8:1.1.1.7.2.5.0.6
	RELENG_4_8_BP:1.1.1.7.2.5
	v8_3_4:1.1.1.12
	RELENG_5_0_0_RELEASE:1.1.1.12
	RELENG_5_0:1.1.1.12.0.2
	RELENG_5_0_BP:1.1.1.12
	RELENG_4_7_0_RELEASE:1.1.1.7.2.5
	RELENG_4_7:1.1.1.7.2.5.0.4
	RELENG_4_7_BP:1.1.1.7.2.5
	RELENG_4_6_2_RELEASE:1.1.1.7.2.5
	RELENG_4_6_1_RELEASE:1.1.1.7.2.5
	v8_3_3:1.1.1.12
	RELENG_4_6_0_RELEASE:1.1.1.7.2.5
	RELENG_4_6:1.1.1.7.2.5.0.2
	RELENG_4_6_BP:1.1.1.7.2.5
	v8_3_2_t1b:1.1.1.12
	v8_3_1:1.1.1.12
	RELENG_4_5_0_RELEASE:1.1.1.7.2.4
	RELENG_4_5:1.1.1.7.2.4.0.4
	RELENG_4_5_BP:1.1.1.7.2.4
	RELENG_4_4_0_RELEASE:1.1.1.7.2.4
	RELENG_4_4:1.1.1.7.2.4.0.2
	RELENG_4_4_BP:1.1.1.7.2.4
	v8_2_4:1.1.1.11
	RELENG_4_3_0_RELEASE:1.1.1.7.2.3
	RELENG_4_3:1.1.1.7.2.3.0.2
	RELENG_4_3_BP:1.1.1.7.2.3
	v8_2_3:1.1.1.10
	RELENG_4_2_0_RELEASE:1.1.1.7.2.2
	v8_2_3_t6b:1.1.1.9
	RELENG_4_1_1_RELEASE:1.1.1.7.2.1
	PRE_SMPNG:1.1.1.8
	RELENG_4_1_0_RELEASE:1.1.1.7.2.1
	RELENG_3_5_0_RELEASE:1.1.1.6.2.1
	v8_2_3_t5b:1.1.1.8
	RELENG_4_0_0_RELEASE:1.1.1.7
	RELENG_4:1.1.1.7.0.2
	RELENG_4_BP:1.1.1.7
	RELENG_3_4_0_RELEASE:1.1.1.6.2.1
	v8_2_2_p5:1.1.1.7
	RELENG_3_3_0_RELEASE:1.1.1.6
	RELENG_3_2_PAO:1.1.1.6.0.4
	RELENG_3_2_PAO_BP:1.1.1.6
	RELENG_3_2_0_RELEASE:1.1.1.6
	RELENG_3_1_0_RELEASE:1.1.1.6
	RELENG_3:1.1.1.6.0.2
	RELENG_3_BP:1.1.1.6
	RELENG_2_2_8_RELEASE:1.1.1.1.2.2
	RELENG_3_0_0_RELEASE:1.1.1.6
	RELENG_2_2_7_RELEASE:1.1.1.1.2.2
	v8_1_2:1.1.1.6
	bind_8_1_2_t3b:1.1.1.5
	bind_v4_9_7_t1b:1.1.1.4
	RELENG_2_2_6_RELEASE:1.1.1.1.2.1
	RELENG_2_2_5_RELEASE:1.1.1.1.2.1
	bind_4_9_6:1.1.1.3
	RELENG_2_2_2_RELEASE:1.1.1.1
	RELENG_2_2_1_RELEASE:1.1.1.1
	RELENG_2_2_0_RELEASE:1.1.1.1
	bind_4_9_5_p1:1.1.1.2
	ISC:1.1.1
	RELENG_2_2:1.1.1.1.0.2
	RELENG_2_2_BP:1.1.1.1
	bind_4_9_4_p1:1.1.1.1
	VIXIE:1.1.1;
locks; strict;
comment	@# @;


1.2
date	2004.09.24.19.48.35;	author des;	state dead;
branches;
next	1.1;

1.1
date	96.08.29.19.20.12;	author peter;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	96.08.29.19.20.12;	author peter;	state Exp;
branches
	1.1.1.1.2.1;
next	1.1.1.2;

1.1.1.2
date	96.12.31.19.49.54;	author peter;	state Exp;
branches;
next	1.1.1.3;

1.1.1.3
date	97.06.27.07.25.08;	author peter;	state Exp;
branches;
next	1.1.1.4;

1.1.1.4
date	98.05.02.10.59.17;	author peter;	state Exp;
branches;
next	1.1.1.5;

1.1.1.5
date	98.05.03.04.09.38;	author peter;	state Exp;
branches;
next	1.1.1.6;

1.1.1.6
date	98.06.11.04.57.24;	author peter;	state Exp;
branches
	1.1.1.6.2.1;
next	1.1.1.7;

1.1.1.7
date	99.11.30.02.41.38;	author peter;	state Exp;
branches
	1.1.1.7.2.1;
next	1.1.1.8;

1.1.1.8
date	2000.05.26.07.17.06;	author asmodai;	state Exp;
branches;
next	1.1.1.9;

1.1.1.9
date	2000.10.31.12.35.23;	author asmodai;	state Exp;
branches;
next	1.1.1.10;

1.1.1.10
date	2001.01.28.23.00.14;	author asmodai;	state Exp;
branches;
next	1.1.1.11;

1.1.1.11
date	2001.07.30.16.51.23;	author asmodai;	state Exp;
branches;
next	1.1.1.12;

1.1.1.12
date	2002.02.04.19.12.33;	author nectar;	state Exp;
branches
	1.1.1.12.8.1;
next	;

1.1.1.12.8.1
date	2004.09.26.03.09.15;	author des;	state dead;
branches;
next	;

1.1.1.7.2.1
date	2000.07.03.22.46.49;	author ps;	state Exp;
branches;
next	1.1.1.7.2.2;

1.1.1.7.2.2
date	2000.11.02.14.07.11;	author asmodai;	state Exp;
branches;
next	1.1.1.7.2.3;

1.1.1.7.2.3
date	2001.01.29.21.43.21;	author asmodai;	state Exp;
branches;
next	1.1.1.7.2.4;

1.1.1.7.2.4
date	2001.08.05.16.02.00;	author asmodai;	state Exp;
branches
	1.1.1.7.2.4.2.1
	1.1.1.7.2.4.4.1;
next	1.1.1.7.2.5;

1.1.1.7.2.5
date	2002.02.17.15.48.30;	author nectar;	state Exp;
branches;
next	;

1.1.1.7.2.4.2.1
date	2002.07.15.08.01.33;	author dougb;	state Exp;
branches;
next	;

1.1.1.7.2.4.4.1
date	2002.07.15.07.55.21;	author dougb;	state Exp;
branches;
next	;

1.1.1.6.2.1
date	99.12.13.15.04.19;	author peter;	state Exp;
branches;
next	1.1.1.6.2.2;

1.1.1.6.2.2
date	2001.01.30.11.52.41;	author asmodai;	state Exp;
branches;
next	;

1.1.1.1.2.1
date	97.06.28.07.36.21;	author peter;	state Exp;
branches;
next	1.1.1.1.2.2;

1.1.1.1.2.2
date	98.05.02.15.56.24;	author peter;	state Exp;
branches;
next	;


desc
@@


1.2
log
@Retire the BIND 8 sources.
@
text
@$Id: INSTALL,v 8.6 1995/12/24 06:43:57 vixie Exp $

THE FILES:
----------
INSTALL		-- This file
README		-- Release announcements, tips and traps (some out of date)
OPTIONS		-- The options that can be turned on and off
RUNSON		-- What machines/compilers is BIND known to build on
TODO		-- Have spare time?  Consider contributing to the project!
doc/info/*	-- Platform-dependent build hints

HOW TO BUILD:
-------------
4.9.3 is considerably easier to build than previous releases.  These
are the instructions on how to compile the software.  For information
on how to create your configuration files (resolv.conf, named.boot, and
zone files) see the doc/bog directory and/or get "DNS and BIND" by C.
Liu and P. Albitz from O'Reilly & Associates, Sebastopol, CA, ISBN
0-937175-82-X 1992

Note:	If you maintain a BSD or are otherwise running a 4.4BSD-based system
	and want to integrate BIND into it, check out BSD/README.

1.  (optional) If you are going to compile for multiple platforms, you
can make a symbolic link tree for each platform to save disk space.  To
create a directory called "sun4.dir", do:
	make DST=sun4.dir links
Now "cd sun4.dir" and you can do everything as if you had a complete
copy of the source.  Just be careful if you are modifying a file, make
sure you turn any links into files:
	mv file file.tmp ; cp file.tmp file ; rm file.tmp

2.  Edit "conf/options.h" and turn on any options that you want.  The
defaults are pretty reasonable for most installations.

3.  Edit "Makefile".  Go to the section that describes your operating
system and uncoment it out.  Add any other variables (for example,
I added a line "DISTHELP=/usr/local/lib".)  If in doubt, use the
default!

4.  "make" should build everything.  Consider putting "./bin" in your
path if "make depend" fails and you think bin/mkdep will help you out.

	*** NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE ***

	The next step (#5) will burn down files which were supplied with
	your operating system.  You should run the suggested "-n" first
	and make sure you have saved any files you want to save.

	*** NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE ***

5.  "make install" will install everything.  You might first do
"make -n install" to see what commands would be executed by "make install"
to make sure you understand where everything is about to be installed.

6.  (optional, SunOS 4.1.x/NetBSD-1.x/Solaris 2.x only): You can integrate
the new resolver (client-side) code into the shared libraries of your
operating system so that all dynamicly linked programs take advantage of
the new resolver.  Read shres/<osname>/INSTALL to find out how to do it.



HOW TO GET HELP:
---------------- 
If you have any problems or fixes send them to
        bind@@uunet.uu.net
 
To be added to that mailing list, send mail to
        bind-request@@uunet.uu.net



This INSTALL was originally written on 15Jul94 by Tom Limoncelli <tal@@plts.org>
Minor changes 23Dec95 by Christopher Davis <ckd@@kei.com>
@


1.1
log
@Initial revision
@
text
@@


1.1.1.1
log
@Take #2.  Import bind-4.9.4-P1 into the intended directory!
This has most of the non-essential stuff removed (ie: what is not built)

bmake glue to follow.
@
text
@@


1.1.1.1.2.1
log
@Update the 2.2 version of bind from 4.9.4-P1 to 4.9.6.  More commits to
follow.
@
text
@d1 1
a1 1
$Id: INSTALL,v 8.8 1997/06/01 20:34:25 vixie Exp vixie $
a9 2
BSD/*           -- How to integrate BIND into a 4.4BSD or 4.4BSD-Lite
contrib/*       -- Useful BIND-related contributions
a10 1
doc/*           -- other RFCs, drafts, papers and
d12 1
a12 1
INTRODUCTION:
d14 6
a19 7
BIND used to be extremely difficult to build.  That changed around
version 4.9.3.  These are the instructions on how to compile the
software.  For information on how to create your configuration files
(resolv.conf, named.boot, and zone files) see the doc/bog directory for
the complete "BIND Operations Guide".  You might also consider getting
"DNS and BIND" by C.  Liu and P.  Albitz from O'Reilly & Associates,
Sebastopol, CA, ISBN 0-937175-82-X 1992
a23 2
BUILDING & INSTALLING:
----------------------
d33 1
a33 12
2. (optional) If you have a typical site, you should find yourself only
editing Makefile and conf/options.h.  Make backups of them now:

	mv conf/options.h conf/options.h.dist
	cp conf/options.h.dist conf/options.h
	chmod u+w conf/options.h

	mv Makefile Makefile.dist
	cp Makefile.dist Makefile
	chmod u+w Makefile

3.  Edit "conf/options.h" and turn on any options that you want.  The
d36 4
a39 6
4.  Edit "Makefile".  The default build parameters are given for 4.4 BSD. 
They should be overridden (not edited!).  Do this by going to the
section that describes your operating system and uncoment the
appropriate lines.  Add any other variables (for example, some people
add "DISTHELP=/usr/local/lib".)  If in doubt, use the default!  Read
the comments carefully!
d41 1
a41 1
5.  "make" should build everything.  Consider putting "./bin" in your
d46 1
a46 1
	The next step (#6) will burn down files which were supplied with
d52 1
a52 1
6.  "make install" will install everything.  You might first do
d56 4
a59 5
7.  (optional, SunOS 4, SunOS 5, NetBSD-1.x, IRIX, Linix only): You can
integrate the new resolver (client-side) code into the shared libraries
of your operating system so that all dynamicly linked programs take
advantage of the new resolver.  Read shres/<osname>/INSTALL to find out
how to do it.
d64 11
a74 16
----------------
The "bind-users@@vix.com" mailing list was created especially for people to
talk about and ask questions about installation, maintenance, etc.  It is
highly recommended that you first help yourself by reading the BOG (doc/bog)
or a book on DNS and BIND.

To be added to this mailing list, send mail to <bind-users-request@@vix.com>

Note that the bind-users mailing list is also available on Usenet as
	comp.protocols.dns.bind
and that we would all prefer that you read it that way if you possibly can.

This INSTALL was...
	originally written on 15Jul94 by Tom Limoncelli <tal@@bell-labs.com>
	changed in minor ways 23Dec95 by Christopher Davis <ckd@@kei.com>
	and then changed by Tom Limoncelli again 16Oct96.
@


1.1.1.1.2.2
log
@Update 2.2 from bind 4.9.6 to 4.9.7-t1b
@
text
@d1 1
a1 1
$Id: INSTALL,v 8.9 1997/06/24 06:43:50 vixie Exp $
@


1.1.1.2
log
@Import Paul Vixie/ISC's bind-4.9.5-patch1 onto the vendor branch.

This has some (all?) of the DNSSEC key management/distribution mechanism
in place.  (The SIG and KEY RR's)

Obtained from: Paul Vixie / ISC / ftp.isc.org
@
text
@d1 1
a1 1
$Id: INSTALL,v 8.7 1996/11/11 06:36:40 vixie Exp $
a9 2
BSD/*           -- How to integrate BIND into a 4.4BSD or 4.4BSD-Lite
contrib/*       -- Useful BIND-related contributions
a10 1
doc/*           -- other RFCs, drafts, papers and
d12 1
a12 1
INTRODUCTION:
d14 6
a19 7
BIND used to be extremely difficult to build.  That changed around
version 4.9.3.  These are the instructions on how to compile the
software.  For information on how to create your configuration files
(resolv.conf, named.boot, and zone files) see the doc/bog directory for
the complete "BIND Operations Guide".  You might also consider getting
"DNS and BIND" by C.  Liu and P.  Albitz from O'Reilly & Associates,
Sebastopol, CA, ISBN 0-937175-82-X 1992
a23 2
BUILDING & INSTALLING:
----------------------
d33 1
a33 12
2. (optional) If you have a typical site, you should find yourself only
editing Makefile and conf/options.h.  Make backups of them now:

	mv Makefile Makefile.tmp
	cp Makefile.tmp Makefile ; rm Makefile.tmp
	chmod u+w Makefile

	mv conf/options.h conf/options.h.tmp
	cp conf/options.h.tmp conf/options.h ; rm conf/options.h.tmp
	chmod u+w conf/options.h

3.  Edit "conf/options.h" and turn on any options that you want.  The
d36 4
a39 6
4.  Edit "Makefile".  The default build parameters are given for 4.4 BSD. 
They should be overridden (not edited!).  Do this by going to the
section that describes your operating system and uncoment the
appropriate lines.  Add any other variables (for example, some people
add "DISTHELP=/usr/local/lib".)  If in doubt, use the default!  Read
the comments carefully!
d41 1
a41 1
5.  "make" should build everything.  Consider putting "./bin" in your
d52 1
a52 1
6.  "make install" will install everything.  You might first do
d56 4
a59 5
7.  (optional, SunOS 4, SunOS 5, NetBSD-1.x, IRIX, Linix only): You can
integrate the new resolver (client-side) code into the shared libraries
of your operating system so that all dynamicly linked programs take
advantage of the new resolver.  Read shres/<osname>/INSTALL to find out
how to do it.
d64 5
a68 7
----------------
The "bind@@uunet.uu.net" mailing list was created especially for people
to talk about and ask questions about installation, maintenance, etc.
It is highly recommended that you first help yourself by reading
the BOG (doc/bog) or a book on DNS and BIND.

To be added to this mailing list, send mail to
d73 2
a74 3
This INSTALL was originally written on 15Jul94 by Tom Limoncelli
<tal@@bell-labs.org> Minor changes 23Dec95 by Christopher Davis
<ckd@@kei.com> and then by Tom Limoncelli 16Oct96.
@


1.1.1.3
log
@Clean (trimmed down) import of bind-4.9.6 onto vendor branch.  This is
to buy time to allow v8.1.1 to be done right rather than rushing it.
@
text
@d1 1
a1 1
$Id: INSTALL,v 8.8 1997/06/01 20:34:25 vixie Exp vixie $
d42 6
a47 2
	mv conf/options.h conf/options.h.dist
	cp conf/options.h.dist conf/options.h
a49 4
	mv Makefile Makefile.dist
	cp Makefile.dist Makefile
	chmod u+w Makefile

d65 1
a65 1
	The next step (#6) will burn down files which were supplied with
d85 13
a97 15
The "bind-users@@vix.com" mailing list was created especially for people to
talk about and ask questions about installation, maintenance, etc.  It is
highly recommended that you first help yourself by reading the BOG (doc/bog)
or a book on DNS and BIND.

To be added to this mailing list, send mail to <bind-users-request@@vix.com>

Note that the bind-users mailing list is also available on Usenet as
	comp.protocols.dns.bind
and that we would all prefer that you read it that way if you possibly can.

This INSTALL was...
	originally written on 15Jul94 by Tom Limoncelli <tal@@bell-labs.com>
	changed in minor ways 23Dec95 by Christopher Davis <ckd@@kei.com>
	and then changed by Tom Limoncelli again 16Oct96.
@


1.1.1.4
log
@Import ISC bind v4.9.7-T1B as a reference.  We may need this if we update
-stable to 4.9.7 instead of 8.1.2 for whatever reason.
@
text
@d1 1
a1 1
$Id: INSTALL,v 8.9 1997/06/24 06:43:50 vixie Exp $
@


1.1.1.5
log
@Import (trimmed) ISC bind-8.1.2-t3b.  This will be updated to 8.1.2 on
final release.

Obtained from:  ftp.isc.org
@
text
@d1 1
a1 1
Supported Systems
d3 97
a99 269
	AIX 4.x
	A/UX 3.1.1
	BSD/OS 2.1, 3.x
	Digital ULTRIX 4.5
	Digital UNIX 3.2C, 4.0
	FreeBSD 2.x, 3.0
	HP MPE
	HP-UX 9.x, 10.20
	IRIX 5.3, 6.2, 6.4
	LynxOS
	NetBSD 1.2, 1.3
	OpenBSD 2.1
	QNX
	Red Hat Linux 4.x, 5.0
	SCO UNIX 3.2v4.2, SCO OSE 5.0.4, UnixWare 2.0.x, 2.1.2
	SunOS 4.1.4
	SunOS 5.5 (Solaris 2.5), 5.6 (Solaris 2.6)

	See port/README for information on porting BIND 8 to other systems.


Building

	If you do not have an ANSI/ISO C compiler, give up or get GCC.  The
	one exception is the ULTRIX compiler, which isn't full ANSI C but it
	has function prototypes and BIND works around the rest.  BIND 8 also
	wants a C library that's ANSI/ISO standard, although it can work
	around some common failings.

	If you do not have yacc, get byacc or GNU bison.  If you do not have
	lex, get GNU flex.  For information on where to get GNU software, see
	http://www.fsf.org/order/ftp.html.

	If you want to build outside the source pool, then

		make DST=/your/destination/here SRC=`pwd` links
		cd /your/destination/here

	If you want to use DST=/var/obj/bind, you can simply type

		make stdlinks

	Next, make sure you have no stale trash laying about

		make clean

	Then, update the Makefile dependencies:

		make depend

	Finally,

		make

	
Installation

	To install, type

		make install

	This will copy binaries to the appropriate locations for your system,
	and install the BIND 8 library and header files under /usr/local/bind.

	The following variables can be used to change where things get
	installed:

		DESTDIR			prefix used in front of all other
					DEST variables.  The default is the
					empty prefix.
		DESTLIB			libraries
		DESTINC			include files
		DESTBIN			ordinary binaries (e.g. dig, nslookup)
		DESTSBIN		system binaries (e.g. named)
		DESTEXEC		helper binaries (e.g. named-xfer)
		DESTHELP		place to put nslookup's help file
		DESTETC			configuration file
		DESTRUN			PID file location

	These variables may be specified on the command line of the 'make'
	or in the Makefile.set for your port (e.g. if you use Solaris, in
	src/port/solaris/Makefile.set).

	Before doing 'make install' using either method, you must

		rm .settings

	in the top level source directory because the build system caches
	these variables.


Using BIND 8 Library Routines

	Until a method to update the system's libraries is available,
	applications wishing to use BIND 8 library routines must include
	BIND 8 .h files, and must link with libbind.a.  E.g.

		cc -I/usr/local/bind/include -c sample.c 
		cc -o sample -L/usr/local/bind/lib sample.o -lbind

	The default locations for libbind.a and .h files in BIND 8.1.1
	and BIND 8.1.2 are different from those used in BIND 8.1-REL.  If
	you did a 'make install' for BIND 8.1-REL, then you should delete
	the files it installed.  They are:

		/usr/local/lib/libbind.a
		/usr/local/include/arpa/inet.h
		/usr/local/include/arpa/nameser.h
		/usr/local/include/arpa/nameser_compat.h
		/usr/local/include/netdb.h
		/usr/local/include/resolv.h
		/usr/local/include/sys/bitypes.h	(if it exists)
		/usr/local/include/sys/cdefs.h		(if it exists)


Operating System Notes

	SunOS 4.1.4

		An ANSI/ISO C compiler is required; we used gcc 2.7.2.1.

	Solaris

		We've tested with Sun's compilers, yacc, and lex, and also
		with gcc, byacc, and flex.  By default, the build will try
		to use gcc.  If you want to use the Sun compilers, simply
		copy "port/solaris/Makefile.set.sun" to
		"port/solaris/Makefile.set".  To go back to using gcc, copy
		"port/solaris/Makefile.set.gcc" to "port/solaris/Makefile.set".

		If you're using a Solaris release earlier than 2.5 and you have
		a large number of interfaces on your system, you many need
		use a script to "limit descriptors N" (where 'N' is a
		suitably large number) before execing "named".  On Solaris
		2.5 and later, the server will do this itself.

	Certain older versions of FreeBSD, NetBSD and BSD/OS

		These systems have a /bin/sh based on "ash", which doesn't
		handle POSIX-style quoting correctly.  Using "bash" will fix
		the problem.  Either run make with "SH=bash" on the command
		line, or edit src/Makefile and change "SH=sh" to "SH=bash".

	QNX

		Read src/port/qnx/README before trying to build.


FD_SETSIZE

	The highest numbered file descriptor that the server and the resolver
	can utilize is determined by the FD_SETSIZE value of the system.  Some
	systems set FD_SETSIZE much smaller than the actual number of files
	that can be opened.  On such systems, create an "fd_setsize.h" file
	that sets FD_SETSIZE appropriately in the port's include directory.


User and Group ID

	Specifying "-u" followed by a username or numeric user id on the
	"named" command line will cause the server to give up all
	privileges and become that user after the initial load of the
	configuation file is complete.  "-g" may be used similarly to set
	the group id.  If "-u" is specified but "-g" is not, the group
	used will be the given user's primary group.

	Here are some hints:

		Because the server will have no privileges after changing
		its user id, you must restart the server if you change the
		interfaces and ports that the server is listening on, or if
		you add an interface.

		If you log to files, you should create all of the log files
		in advance (e.g. with "touch"), and make sure they are owned
		by the user and group "named" will be running as.

		You'll have to edit "ndc" to get it to start the server
		with the appropriate flags.

	Note: this feature is still experimental.


Chroot

	"-t" followed by a directory path on the "named" command line will
	cause the server to chroot() to that directory before it starts
	loading the configuration file.

	Setting up a chrooted area varies somewhat by operating system.  Some
	experimentation may be necessary.  Here are some hints:

		Don't forget to install named-xfer.

		Either don't use shared libraries when you build, or do
		whatever is required on your OS to allow shared libraries
		to be used after a chroot().

		syslog() is often troublesome after chrooting.  Use the
		"logging" statement and log to a file instead.

		/dev/null should be in the chroot directory hierarchy.  You
		can usually find out the mknod parameters for a null device by
		looking in /dev/MAKEDEV.

		You'll have to edit "ndc" to get it to start the server
		with the appropriate flags, and to use the right pid file.

	Note: this feature is still experimental.


Using the Server

	Note that /etc/named.boot is long gone.  You need to make yourself an
	/etc/named.conf (note, that ends in "conf" rather than "boot") file.
	This file looks a lot like a C program or a modern gated.conf file;
	there are lots of {curly braces} and it takes some getting used to.
	You may get a lot more help from the example file (which is
	bin/named/named.conf) than from the documentation (see ../doc/html).
	You can convert your named.boot file to a named.conf file if you have
	Perl; see bin/named/named-bootconf.pl.

	All the files that used to be created in /var/tmp, e.g. named.run,
	will now be created in the directory specified in the options
	statement.  If debugging is turned on using the "-d" flag on server
	startup, then named.run will be created in the current directory.


Known Dynamic DNS Bugs

	If the server is master for a zone and authoritative for a child of
	that zone, then a dynamic update to the parent will destroy the
	delegation to the child when the parent zone is written to disk.
	This problem will be fixed in a future release.  The only workaround
	is to not be authoritative for child zones of a dynamic zone.

	Slave servers do not forward update requests to the primary master
	correctly.  This will be fixed in a future release.  In the meantime,
	slaves will refuse dynamic updates.


Shared Libraries

	Absolutely no support exists for editing the system's shared
	libraries to update the resolver.  If you want to do that you
	probably want to look at BIND Version 4 (see http://www.isc.org/isc/)
	or wait a while or help out a lot.  This means you probably do not
	want to install the library or include files into /usr/lib or
	/usr/include, and this kit helpfully puts everything into
	/usr/local/lib and /usr/local/include for that reason among others.


Notes about contrib and doc

	The BIND 8 "doc" package includes HTML documentation as	well as all
	the RFC's, Internet Drafts, and "man" pages we can think of.  You may
	need to install the doc/tmac files in your nroff/troff support
	directory since we use the newer BSD "mandoc" system for our "man"
	pages.

	The BIND 8 "contrib" package is full of junk that you may want to
	take a look at.  Feel free to send us more junk for future releases.


Bugs

	Please report bugs to

		bind-bugs@@isc.org
@


1.1.1.6
log
@Import final bind-8.1.2 release.

Obtained from: ftp.isc.org
@
text
@d82 3
a84 2
	These variables should be specified in the Makefile.set for your
	port (e.g. if you use Solaris, in src/port/solaris/Makefile.set).
d86 1
a86 1
	Before doing 'make install', you must
d120 1
a120 1
	AIX
d122 1
a122 19
		Build problems have been reported with the AIX "make".
		We recommend using GNU "make" instead.

	Linux

		"make links" and "make stdlinks" cause problems on
		some Linux kernels because there are too many levels of
		symbolic links.

	QNX

		Read src/port/qnx/README before trying to build.

	SCO 5.0.x

		To build using gcc, copy "port/sco50/Makefile.set.gcc" to
		"port/sco50/Makefile.set".  To go back to using SCO's
		compilers, copy "port/sco50/Makefile.set.sco" to
		"port/sco50/Makefile.set".
a138 4
	SunOS 4.1.4

		An ANSI/ISO C compiler is required; we used gcc 2.7.2.1.

d145 5
@


1.1.1.6.2.1
log
@MFC: bind 8.2.2.p5

Urged by:	imp, alfred, and a whole bunch of other folks.
Approved by:	jkh (a few days ago)
@
text
@d1 1
a1 12
Systems it is known to compile and run on:

	BSD/OS 3.1, 4.0.1
	FreeBSD 3.1, 3.2, 3.3
	RH Linux 5.2 (don't use "make links" when building, though)
	Debian GNU/Linux 2.2.9 ("unreleased")
	Digital UNIX 3.2C, 4.0, 5.0
	NetBSD/i386 1.3.2, 1.4
	SunOS 5.6 (Solaris 2.6), SunOS 5.7 (Solaris 7)
	SCO UnixWare 7.0, 7.0.1, 7.1

Systems it has been known in the past to compile and run on:
d5 1
d7 2
d16 1
d19 1
a19 1
	SunOS 5.5 (Solaris 2.5)
a52 2
	NOTE: "make depend" is a NO-OP for these platforms: AIX, HPUX and NeXT.

d55 1
a55 1
		make all
d72 1
a72 3
					empty prefix. (for non-root installs;
					not equivalent to autoconf's --prefix)

a78 1
		DESTMAN			man file location
d80 1
a80 3
		DESTRUN			PID file location and "ndc" control
					channel location.  This cannot be the
					same directory as DESTSBIN.
a122 4
	
	FreeBSD, NetBSD, OpenBSD and BSDI
		The kit should compile even if you have intalled the KAME
		IPv6 kit.
a158 4

	NeXT

		Read src/port/next/README.FIRST before trying to build.
@


1.1.1.6.2.2
log
@MFC:	8.2.3
@
text
@d4 1
a4 1
	FreeBSD 3.3, 3.4
a8 1
	Darwin 1.x (Mac OS X)
a10 1
	IRIX 6.5
d16 1
a16 1
	Digital ULTRIX 4.5 (without Compaq's Y2K kit installed)
a20 1
	FreeBSD 3.1, 3.2
a141 6
	IRIX
		build problems have been reported w/ IRIX 6.3, res_debug.c
		and #include <stdlib.h>.  You may need to comment out
		the #include <stdlib.h> and declare
		"void *malloc(size_t size)" to get named to compile on 6.3.

d169 1
a169 1
		a large number of interfaces on your system, you many need to
d260 2
a261 5
	You can convert your named.boot file to a named.conf file using
	bin/named-bootconf/named-bootconf.

	e.g.
		named-bootconf < /etc/named.boot > /etc/named.conf
@


1.1.1.7
log
@Import bind v8.2.2.p5, minus the crypto for the time being.  The bind
package does have BXA export approval, but the licensing strings on the
dnssafe code are a bit unpleasant.  The crypto is easy to restore and bind
will run without it - just without full dnssec support.

Obtained from:	The Internet Software Consortium (www.isc.org)
@
text
@d1 1
a1 12
Systems it is known to compile and run on:

	BSD/OS 3.1, 4.0.1
	FreeBSD 3.1, 3.2, 3.3
	RH Linux 5.2 (don't use "make links" when building, though)
	Debian GNU/Linux 2.2.9 ("unreleased")
	Digital UNIX 3.2C, 4.0, 5.0
	NetBSD/i386 1.3.2, 1.4
	SunOS 5.6 (Solaris 2.6), SunOS 5.7 (Solaris 7)
	SCO UnixWare 7.0, 7.0.1, 7.1

Systems it has been known in the past to compile and run on:
d5 1
d7 2
d16 1
d19 1
a19 1
	SunOS 5.5 (Solaris 2.5)
a52 2
	NOTE: "make depend" is a NO-OP for these platforms: AIX, HPUX and NeXT.

d55 1
a55 1
		make all
d72 1
a72 3
					empty prefix. (for non-root installs;
					not equivalent to autoconf's --prefix)

a78 1
		DESTMAN			man file location
d80 1
a80 3
		DESTRUN			PID file location and "ndc" control
					channel location.  This cannot be the
					same directory as DESTSBIN.
a122 4
	
	FreeBSD, NetBSD, OpenBSD and BSDI
		The kit should compile even if you have intalled the KAME
		IPv6 kit.
a158 4

	NeXT

		Read src/port/next/README.FIRST before trying to build.
@


1.1.1.7.2.1
log
@MFC: bind 8.2.3-T5B
@
text
@d4 1
a4 1
	FreeBSD 3.3, 3.4
a10 1
	IRIX 6.5
d16 1
a16 1
	Digital ULTRIX 4.5 (without Compaq's Y2K kit installed)
a20 1
	FreeBSD 3.1, 3.2
a140 6

	IRIX
		build problems have been reported w/ IRIX 6.3, res_debug.c
		and #include <stdlib.h>.  You may need to comment out
		the #include <stdlib.h> and declare
		"void *malloc(size_t size)" to get named to compile on 6.3.
@


1.1.1.7.2.2
log
@Fix and resolve conflicts of the BIND 8.2.3-T6B MFC.

Approved by:	jkh
@
text
@a8 1
	Darwin 1.x (Mac OS X)
d268 2
a269 5
	You can convert your named.boot file to a named.conf file using
	bin/named-bootconf/named-bootconf.

	e.g.
		named-bootconf < /etc/named.boot > /etc/named.conf
@


1.1.1.7.2.3
log
@MFC:	BIND 8.2.3
@
text
@d178 1
a178 1
		a large number of interfaces on your system, you many need to
@


1.1.1.7.2.4
log
@Fix conflicts after MFC of BIND 8.2.4.
@
text
@d63 1
a63 1
	NOTE: "make depend" is a NO-OP for some platforms, but always harmless.
a139 5

	AIX4 with Linux Compatibility API

		May need to define HAVE_STRNDUP in
		port/aix4/include/port_after.h.
a141 1

a144 8
	HPUX

		If you are using gcc you may have to remove the '-ansi'
		flag.  This is gcc version dependent.

		HPUX 10.20 early versions of the HP C/ANSI C compiler do
		not work, version B.10.20.15 in known to work.

a145 1

@


1.1.1.7.2.4.2.1
log
@Upgrade to version 8.3.3.

Approved by:	security-officer
@
text
@a205 4
	MPE/iX	IPv6 is *not* supported. src/port/mpe/recvfrom.c needs to
		be re-written to support IPv6 if and when the OS supports
		IPv6.

@


1.1.1.7.2.4.4.1
log
@Upgrade to version 8.3.3.

Approved by:	security-officer
@
text
@a205 4
	MPE/iX	IPv6 is *not* supported. src/port/mpe/recvfrom.c needs to
		be re-written to support IPv6 if and when the OS supports
		IPv6.

@


1.1.1.7.2.5
log
@MFC: ISC BIND 8.3.1-REL.
@
text
@a205 4
	MPE/iX	IPv6 is *not* supported. src/port/mpe/recvfrom.c needs to
		be re-written to support IPv6 if and when the OS supports
		IPv6.

@


1.1.1.8
log
@Virgin import of BIND v8.2.3-T5B
@
text
@d4 1
a4 1
	FreeBSD 3.3, 3.4
a10 1
	IRIX 6.5
d16 1
a16 1
	Digital ULTRIX 4.5 (without Compaq's Y2K kit installed)
a20 1
	FreeBSD 3.1, 3.2
a140 6

	IRIX
		build problems have been reported w/ IRIX 6.3, res_debug.c
		and #include <stdlib.h>.  You may need to comment out
		the #include <stdlib.h> and declare
		"void *malloc(size_t size)" to get named to compile on 6.3.
@


1.1.1.9
log
@Virgin import of BIND v8.2.3-T6B
@
text
@a8 1
	Darwin 1.x (Mac OS X)
d268 2
a269 5
	You can convert your named.boot file to a named.conf file using
	bin/named-bootconf/named-bootconf.

	e.g.
		named-bootconf < /etc/named.boot > /etc/named.conf
@


1.1.1.10
log
@Virgin import of BIND v8.2.3-REL
@
text
@d178 1
a178 1
		a large number of interfaces on your system, you many need to
@


1.1.1.11
log
@Virgin import of BIND v8.2.4-REL
@
text
@d63 1
a63 1
	NOTE: "make depend" is a NO-OP for some platforms, but always harmless.
a139 5

	AIX4 with Linux Compatibility API

		May need to define HAVE_STRNDUP in
		port/aix4/include/port_after.h.
a141 1

a144 8
	HPUX

		If you are using gcc you may have to remove the '-ansi'
		flag.  This is gcc version dependent.

		HPUX 10.20 early versions of the HP C/ANSI C compiler do
		not work, version B.10.20.15 in known to work.

a145 1

@


1.1.1.12
log
@Import of ISC BIND 8.3.1-REL.
@
text
@a205 4
	MPE/iX	IPv6 is *not* supported. src/port/mpe/recvfrom.c needs to
		be re-written to support IPv6 if and when the OS supports
		IPv6.

@


1.1.1.12.8.1
log
@MFC: BIND 9 and related bits.

Approved by:	re
@
text
@@


