head	1.2;
access;
symbols
	RELENG_5_5_0_RELEASE:1.1.1.16.4.1
	RELENG_5_5:1.1.1.16.4.1.0.6
	RELENG_5_5_BP:1.1.1.16.4.1
	RELENG_5_4_0_RELEASE:1.1.1.16.4.1
	RELENG_5_4:1.1.1.16.4.1.0.4
	RELENG_5_4_BP:1.1.1.16.4.1
	RELENG_4_11_0_RELEASE:1.1.1.7.2.9
	RELENG_4_11:1.1.1.7.2.9.0.4
	RELENG_4_11_BP:1.1.1.7.2.9
	RELENG_5_3_0_RELEASE:1.1.1.16.4.1
	RELENG_5_3:1.1.1.16.4.1.0.2
	RELENG_5_3_BP:1.1.1.16.4.1
	RELENG_5:1.1.1.16.0.4
	RELENG_5_BP:1.1.1.16
	RELENG_4_10_0_RELEASE:1.1.1.7.2.9
	RELENG_4_10:1.1.1.7.2.9.0.2
	RELENG_4_10_BP:1.1.1.7.2.9
	RELENG_5_2_1_RELEASE:1.1.1.16
	RELENG_5_2_0_RELEASE:1.1.1.16
	RELENG_5_2:1.1.1.16.0.2
	RELENG_5_2_BP:1.1.1.16
	v8_3_7:1.1.1.16
	RELENG_4_9_0_RELEASE:1.1.1.7.2.8
	RELENG_4_9:1.1.1.7.2.8.0.2
	RELENG_4_9_BP:1.1.1.7.2.8
	v8_3_6:1.1.1.15
	RELENG_5_1_0_RELEASE:1.1.1.14
	RELENG_5_1:1.1.1.14.0.2
	RELENG_5_1_BP:1.1.1.14
	RELENG_4_8_0_RELEASE:1.1.1.7.2.7
	RELENG_4_8:1.1.1.7.2.7.0.2
	RELENG_4_8_BP:1.1.1.7.2.7
	v8_3_4:1.1.1.14
	RELENG_5_0_0_RELEASE:1.1.1.13
	RELENG_5_0:1.1.1.13.0.2
	RELENG_5_0_BP:1.1.1.13
	RELENG_4_7_0_RELEASE:1.1.1.7.2.6
	RELENG_4_7:1.1.1.7.2.6.0.2
	RELENG_4_7_BP:1.1.1.7.2.6
	RELENG_4_6_2_RELEASE:1.1.1.7.2.5.2.1
	RELENG_4_6_1_RELEASE:1.1.1.7.2.5.2.1
	v8_3_3:1.1.1.13
	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.11
	RELENG_4_5_0_RELEASE:1.1.1.7.2.3
	RELENG_4_5:1.1.1.7.2.3.0.4
	RELENG_4_5_BP:1.1.1.7.2.3
	RELENG_4_4_0_RELEASE:1.1.1.7.2.3
	RELENG_4_4:1.1.1.7.2.3.0.2
	RELENG_4_4_BP:1.1.1.7.2.3
	v8_2_4:1.1.1.10
	RELENG_4_3_0_RELEASE:1.1.1.7.2.2
	RELENG_4_3:1.1.1.7.2.2.0.2
	RELENG_4_3_BP:1.1.1.7.2.2
	v8_2_3:1.1.1.9
	RELENG_4_2_0_RELEASE:1.1.1.7.2.1
	v8_2_3_t6b:1.1.1.8
	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.51;	author peter;	state Exp;
branches;
next	1.1.1.3;

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

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

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

1.1.1.6
date	98.06.11.04.57.27;	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.39;	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	2001.01.28.23.00.14;	author asmodai;	state Exp;
branches;
next	1.1.1.10;

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

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

1.1.1.12
date	2002.05.13.19.31.46;	author nectar;	state Exp;
branches;
next	1.1.1.13;

1.1.1.13
date	2002.07.01.01.05.53;	author dougb;	state Exp;
branches;
next	1.1.1.14;

1.1.1.14
date	2003.01.28.13.07.25;	author dougb;	state Exp;
branches;
next	1.1.1.15;

1.1.1.15
date	2003.06.17.08.23.21;	author dougb;	state Exp;
branches;
next	1.1.1.16;

1.1.1.16
date	2003.11.28.21.57.57;	author dougb;	state Exp;
branches
	1.1.1.16.4.1;
next	;

1.1.1.16.4.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	2001.01.29.21.43.21;	author asmodai;	state Exp;
branches;
next	1.1.1.7.2.3;

1.1.1.7.2.3
date	2001.08.05.16.02.00;	author asmodai;	state Exp;
branches
	1.1.1.7.2.3.2.1
	1.1.1.7.2.3.4.1;
next	1.1.1.7.2.4;

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

1.1.1.7.2.5
date	2002.05.15.19.51.18;	author nectar;	state Exp;
branches
	1.1.1.7.2.5.2.1;
next	1.1.1.7.2.6;

1.1.1.7.2.6
date	2002.07.07.08.19.01;	author dougb;	state Exp;
branches;
next	1.1.1.7.2.7;

1.1.1.7.2.7
date	2003.01.29.02.52.20;	author dougb;	state Exp;
branches;
next	1.1.1.7.2.8;

1.1.1.7.2.8
date	2003.08.25.21.07.47;	author dougb;	state Exp;
branches;
next	1.1.1.7.2.9;

1.1.1.7.2.9
date	2003.11.28.22.13.47;	author dougb;	state Exp;
branches;
next	;

1.1.1.7.2.5.2.1
date	2002.07.15.07.51.03;	author dougb;	state Exp;
branches;
next	;

1.1.1.7.2.3.2.1
date	2002.07.15.08.01.34;	author dougb;	state Exp;
branches;
next	;

1.1.1.7.2.3.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.21;	author peter;	state Exp;
branches;
next	1.1.1.6.2.2;

1.1.1.6.2.2
date	2000.11.27.14.46.47;	author asmodai;	state Exp;
branches;
next	1.1.1.6.2.3;

1.1.1.6.2.3
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.22;	author peter;	state Exp;
branches;
next	1.1.1.1.2.2;

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


desc
@@


1.2
log
@Retire the BIND 8 sources.
@
text
@The official way to get BIND is:	ftp ftp.vix.com
					cd pub/bind/release
					binary
					get bind.tar.gz

The official mailing lists are:		bind-users@@vix.com	- users/admins
  (use *-request@@* for admin mail)	bind-workers@@vix.com	- developers

The official Usenet newsgroups are:	comp.protocols.tcp-ip.domains
					
BIND is currently sponsored by:		The Internet Software Consortium
					(send to <info@@isc.org> for details.)

----- 4.9.3 BETA33 - December, 1995 - paul@@vix.com

Take a look around in doc/misc/ and contrib/.  Reread INSTALL.  Have fun.

----- 4.9.3 BETA11, BETA12 release - December, 1994 - paul@@vix.com

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.

Read the top of CHANGES for interesting stuff.

Don't forget to purge all your secondary zone files before upgrading to this
BIND if your existing one came from a vendor.

The NOTIFY feature is turned off by default, but it's really cool and you
should consider turning it on if you are willing to risk having it not work
after the RFC process is complete (if the protocol has to change at all.)
It already does not conform to the draft protocol so you should consider it
"experimental" even if it happens to work fine.

----- 4.9.3 BETA10 release - August, 1994 - paul@@vix.com

I recommend reading this ENTIRE FILE before you attempt to build or use BIND.
However, you can get started quickly by scanning down this file for "QUICK" in
the right margin and just reading those sections.  You can also look at the
INSTALL file.  You should look at doc/info/* if you have trouble building.

There are at least two known bugs in this BIND:

1.	if you have two authoritative zones (primary or secondary) where
	one is a subzone of the other, e.g.,
		primary	pa.dec.com	z/pa.dec.com
		primary dec.com		z/dec.com
	and you remove or comment out the subzone (pa.dec.com in our example)
	and SIGHUP named, the delegation and other RR's at "pa.dec.com" will
	be missing from your cache.  to avoid this, you should "named.restart"
	rather than SIGHUP ("named.reload") when making changes of this kind.

2.	the /HS qualifier doesn't work on "cache" directives.  you will have
	to put your hesiod root information into your main "root.cache" file.

Also, you may find that your utilities will not link with this -lresolv
unless you also install lib44bsd.a and link with -lresolv -l44bsd.  This
is because older systems do not include inet_aton() and other functions.

----- 4.9.3 BETA6 release - June, 1994 - paul@@vix.com

Several private beta test releases have come and gone, and we've fixed a
number of things.  See CHANGES for details.

There is a new Sun Shared Library update mechanism in place, and it works
quite well.  See shres/*.  

Versions of NSLOOKUP up through BIND 4.8.3's used IQUERY to ask the local
server for information about the server's own name.  I assume that this was
done in a "what the heck, nothing uses these, how can we contrive a need?"
sort of spirit.  I removed this code as of BIND 4.9's NSLOOKUP and had it
use the standard gethostbyaddr() mechanisms (which depend on normal queries
of PTR data).  Disabling INVQ and putting "options fake-iquery" in the boot
file will cause IQUERY to be answered bogusly but in a way that old nslookup
programs won't trip on.  INVQ is disabled by default in conf/options.h.

----- 4.9.3 BETA2 release - June, 1994 - paul@@vix.com

News flash! BIND development is now funded by the Internet Software Consortium.

Look at CHANGES to see what's new.  Check out doc/misc to see some interesting
papers from Purdue (and Bell Labs, if we're lucky) on DNS security that
motivated many of the security-related changes present in this release.

Check out shres/Makefile for SunOS4 shared library support.

INVQ now defaults to "undef".  See OPTIONS and conf/options.h.

ALLOW_UPDATES is no longer available, and will be removed next release.

You should look hard at the SENSIBLE_DOTS option and convert your serial 
numbers either to "sensible" ones or ones without dots (YYYYMMDD## preferred).
SENSIBLE_DOTS will be the default in the next release.

NCACHE and VALIDATE are _working_ now.

Read the BOG!  It's been updated since the previous release.

If you are a vendor and are including some or all of this code in your product,
please drop me a line to let me know.  I field a lot of questions about BIND
and it is helpful for me to know which vendor releases contain which versions
of BIND.  It's also helpful for me to have contacts within the engineering
groups of the various vendors, since when I find a heinous bug I can let you
know.

----- 4.9.2 FINAL (940221) release - February, 1994 - paul@@vix.com

If you look at the last entry in TODO, you'll see that there are a lot
of things in the queue waiting to go in.  However, I'm holding the line
so that 4.9.2-FINAL can be the same as what goes out with 4.4BSD-Lite.
I expect to open 4.9.3-ALPHA fairly soon, with patches comprising new
work; 4.9.2-FINAL will have patches released for it only to correct bugs.

The official way to get BIND 4.9.2 is:	ftp gatekeeper.dec.com	OUT OF DATE!!!
					cd pub/misc/vixie	OUT OF DATE!!!
					binary			OUT OF DATE!!!
					get bind-940221.tar.gz	OUT OF DATE!!!
				   or:	get bind-940221.tar.Z	OUT OF DATE!!!

The official mailing lists are:		bind-users@@vix.com	- users/admins
  (use *-request for admin mail)	bind-workers@@vix.com	- developers

The official Usenet newsgroups are:	comp.protocols.tcp-ip.domains
					
My official e-mail address is:		paul@@vix.com

----- 4.9.2 BETA5 (931205) release - December, 1993 - paul@@vix.com

no comments; see CHANGES file.

----- 4.9.2 BETA4 (931104) release - November, 1993 - paul@@vix.com

All reported portability problems have been fixed.  All core dumps have
had changes made for them and we are ready to have them tested again.  As
usual, I am running this in production on my own zones and I am rather
confident in it.  Note, again, that this is a BETA release and you should
not put it up for anon-ftp or otherwise republish it in any way.

----- 4.9.2 ALPHA2 (930908) release - September, 1993 - paul@@vix.com

4.9.2 has fixes for most of the bugs that smb@@bellcore's white paper talked
about, and CERT is going to be knocking on vendor's doors to get it shipped
with as many operating systems as possible.

----- 4.9.2 ALPHA1 (930506) release - July, 1993 - Paul Vixie <paul@@vix.com>

I don't work for DEC any more, so note the new e-mail address.  The old
<bind-4.9@@pa.dec.com> list has been moved to <bind-workers@@vix.com>; if
you intend to help hack BIND and you want to be advised of alpha-testing
releases, send mail to <bind-workers-request@@vix.com> and ask to be added
to the list.

Note that 4.9.1 was an interrim, nonpublished release intended to catch
the porting changes needed for 4.4BSD.  It never really existed separately.

----- 4.9 release - April, 1993 - Paul Vixie <vixie@@pa.dec.com>

For information on what's new in 4.9, see OPTIONS and CHANGES.  Also note
that the man page for named(8) in man/named.8, and the entire Bind Operations
Guide in doc/BOG/*, has been updated for 4.9.  Both make excellent reading.

Those of you who are thinking of adding features should first read TODO to
see if someone else has already indicated an intention to work on the same
thing.  If your feature is significant you should ask <bind-workers@@vix.com>
before you hack, if for no other reason than to tell other maintainers to
expect a patch soon.

Note that the resolver has a number of routines that may already be present
on your system.  Efforts have been made to avoid generating code for them on
systems where they aren't needed; don't worry about them if they're
generated unneccessarily since the linker will sort things out.

This software is protected under the U C Regents' copyright.  Changes made
by or released through Digital Equipment Corporation are subject to a
subsidiary copyright.  The entire copyright is as follows:

++Copyright++ 1989
-
Copyright (c) 1989
   The Regents of the University of California.  All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
   must display the following acknowledgement:
	This product includes software developed by the University of
	California, Berkeley and its contributors.
4. Neither the name of the University nor the names of its contributors
   may be used to endorse or promote products derived from this software
   without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
-
Portions Copyright (c) 1993 by Digital Equipment Corporation.

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, and that
the name of Digital Equipment Corporation not be used in advertising or
publicity pertaining to distribution of the document or software without
specific, written prior permission.

THE SOFTWARE IS PROVIDED "AS IS" AND DIGITAL EQUIPMENT CORP. DISCLAIMS ALL
WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS.   IN NO EVENT SHALL DIGITAL EQUIPMENT
CORPORATION 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.
-
--Copyright--

To build this:								QUICK

	(on SUNOS, use the BSD build environment or you will
	get the wrong definition for O_NDELAY)

	look at conf/options.h and edit to your tastes.
	The OPTIONS file here in this directory will help you
	figure out what to do.

	You should also look at the Makefile to select the proper set
	of definitions depending on whether you are using Ultrix,
	SunOS, and other 4.[23] BSD-alikes or using BSD 4.4, BSD/386,
	and other net2-alikes.

	"make links" will build a shadow source tree full
	of symbolic links.  the default name of this tree
	is "./native.b", but you can override it by setting
	the DST variable on the "make" command line, as in:
		make DST=vax.b SRC=..
	if your DST is not a subdir of "here", you will need to
	override the SRC variable's default (which is ".."),
	as in:
		make DST=/tmp/vax.b SRC=`pwd` 
	note that the DST directory must be nonexistent at
	the time that you run "make links".

	after "make links", you can cd to the new build
	directory, check the settings in the Makefile, and
	run "make depend".  if you aren't using "make links"
	(shame on you), just use "make depend" from "here".
	"make depend" may fail on your system; if so, look in
	the bin/ directory and find a mkdep that does in fact
	work for you.

	if you skip the "make depend" phase, or after you run it,
	you can do "make all" (from the build directory if you
	used "make links" or from "here" if you're just hacking
	around).  you will get the following new things out of it:
		res/libresolv.a
		compat/lib/lib44bsd.a (optional)
		include/{netdb,resolv}.h
		include/arpa/{inet,nameser}.h
		compat/include/sys/{cdefs,bitypes}.h
		tools/{nstest,nsquery,dig,host}
		tools/nslookup/nslookup
		named/named
		named/named-xfer
	if you have trouble with "make all", check conf/portability.h
	for things that your system needs, or doesn't need, or whatever.
	it is preferable to add #ifdef's to conf/portability.h than to
	add them anywhere else.
	
	from the build directory (or "here" if you didn't
	use "make links"), you can try "make -n install"
	which will tell you what will be installed.  it might
	actually be right; however, what you will probably have to
	do is copy the above files into the places you want
	run them from.  the other files you will need are:
		tools/nslookup/nslookup.help
		named/named.restart
		named/named.reload

	resolver library notes: to install it, either put the .a
	file into /usr/local/lib or /usr/lib (if you use -lresolv
	on all the links of your networking software), or use "ar"
	to put all res/*.o directly into your /lib/libc.a file.
	either way you will want to copy the include files
	(including those from compat/include/sys) over to
	/usr/include (or /usr/local/include if you're willing to
	use -I/usr/local/include on all your network-software
	compiles).  something like this:
	    cp res/libresolv.a /usr/lib; ranlib /usr/lib/libresolv.a
	    tar chf - include | (cd /usr/include; tar xvpf -)
	    cp compat/include/sys/*.h /usr/include/sys

	installing the man pages is left as an exercise for the
	reader.  there are just too many different versions of
	"man" floating around for me to be able to help you figure
	out what to do for the one you happen to be using.

	WARNING: If you were running a BIND 4.8.3 or earlier based
	named you should remove all cache files prior to starting
	named. It would generally be a good idea to remove all cache
	files regardless when installing a new version. The creadability
	code depends upon the cache files having been made with the
	latest named-xfer for correct operation.

(special compilation-related warning about SunOS systems:)

	From: Tom Limoncelli
	To: vixie (Paul A Vixie)
	Date: Mon, 11 Jan 93 11:30:39 EST

	Sun compiler v2.0.1 hates bind4.9 code.

	Sun has 3 compilers:

	/usr/ucb/cc  -- the default for SunOS 4.1.[123],
			dropped in Solaris 2.0.
	/usr/lang/cc  -- the "unbundled" cc v1.0
			(pretty good, but expensive), only
	                 generates code for SunOS 4.1.x.
	/usr/lang/cc.2.0.1 -- the latest "unbundled" cc,
			for when they stop shipping the
			bundled version altogether.  This
			generates code for SunOS 4.1.x and Solaris 2.x.

	Sun's 2.0.1 C compiler (the one with the floating licenses) for SunOS
	4.1.x outputs a HUGE number of warnings.  They can be ignored.

--------------------- (4.8.3 README -- mostly obsolete now)

This directory contains all the info and sources
for the Berkeley Internet Name Domain server.
You should read and understand these directions before starting
to install the libraries and nameserver.  Some of these steps
replace existing source and binary files; you should make backups
of all existing files before you begin this installation.
Two installation procedures are described.  The first is for 4.3BSD
and other similar systems that are already configured to use earlier
versions of the nameserver, and which have the new version of <netdb.h>
(containing a h_addr_list field in the hostent structure).  The second
procedure is for 4.2BSD and derived systems.  This procedure requires
more decisions to be made, and may have to be varied due to system
or operation constraints.

The subdirectories and their contents are:

bin       - shell scripts used by current Berkeley makefiles
man       - manual pages & documentation
doc       - copy of Bind Operations Guide, and other documents 
include   - include files to go in /usr/include
named     - name server sources
res       - source for C library resolver routines (and other libc additions)
	    (may be used as separate library, resolv.a)
conf/master - Sample data files
tools     - some test programs


Here is how to install the name server on 4.3BSD:

0) cp bin/mkdep.append /usr/ucb/mkdep
   cp bin/manroff /usr/man/manroff
1) cp include/arpa/nameser.h /usr/include/arpa  
2) cp include/*.h /usr/include 
3) cp man/*.1 /usr/man/manl
   cp man/*.3 /usr/man/man3
   cp man/*.5 /usr/man/man5
   cp man/*.7 /usr/man/man7
   cp man/*.8 /usr/man/man8
4) NOTE: Don't install the Makefiles on 4.3 Tahoe Release
   cp res/{res*.c,herror.c} /usr/src/lib/libc/net
   cp res/Makefile.libc.net /usr/src/lib/libc/net/Makefile
   cp res/strcasecmp.c /usr/src/lib/libc/gen
   cp res/strpbrk.c /usr/src/lib/libc/compat-sys5
   cp res/named/{*.c,Makefile} /usr/src/lib/libc/net/named
5) add strcasecmp.[co] to the Makefile in /usr/src/lib/libc/gen
6) add strpbrk.[co] to the Makefile in /usr/src/lib/libc/compat-sys5
7) rebuild and install /lib/libc.a.
8) edit named/pathnames.h to correpond with your system's configuration
9) cd named; make depend; make all; make install
10) cd tools/nslookup; make nslookup; make install
11) create the master files (samples in conf/master/*)
12) edit /etc/rc.local to include:

if [ -f /etc/named ]; then
        /etc/named; echo -n ' named' >/dev/console
fi

13) recompile network client and server programs that use gethostbyname, etc.


Here is how to install the name server on 4.2BSD or similar systems.
First, a few notes on the choices that must be made.

Rather than building libresolv.a, you may wish to integrate the resolver
routines into /lib/libc.a.  This is recommended to make it easy to recompile
network programs once named is running.  This procedure may require hand-
tayloring on some systems.

You will have to choose a version of mkdep from the bin directory
that will work on your system:
If you've modified make(1) to use .depend files as described
in the current sendmail distribution, use mkdep; otherwise,
if you have the 4.3BSD cc -M option, use mkdep.append; on ultrix,
use mkdep.ultrix (uses cc -Em); otherwise, use mkdep.old.compiler.
The mkdep script is used by "make depend" to regenerate Makefile dependency
lists.

You will need to chose a version of netdb.h.  First, check /usr/include/netdb.h
on your system.  If the hostent structure has a h_addr_list entry, you can
probably use your existing netdb.h or the one in include/netdb.h.
If the existing netdb.h in /usr/include does not have a h_addr_list field,
you will have to decide whether to update to the 4.3BSD format of the hostent
structure.  This is the best approach, but cannot be used unless you plan
to upgrade entirely: if you use the new structure in /usr/include/resolv.h,
you must recompile everything that uses the hostent structure, including
the rest of the C library and all networking programs, without using
any pre-existing object files.  If this isn't possible or desirable,
and /usr/include/netdb.h doesn't have an h_addr_list line, use
include/netdb.h.4.2 instead of netdb.h.  The other version of netdb.h
(include/netdb.h.4.2.compat) may be used instead of include/netdb.h.4.2.
This version along with a change in res/named/gethostnamadr.c.compat
provide for using the new format of the hostent structure while having
binary compatibility with existing libraries.

On systems with Sun RPC, you will have to merge include/netdb.h or
include/netdb.h.4.2 with /usr/include/netdb.h; copy the rpc-related lines
into the appropriate copy of netdb.h.  Alternatively, use an alternate
include path when compiling the resolver library and programs that use it.

0) cp bin/{whatever} /usr/ucb/mkdep		(see above)
   cp bin/manroff /usr/man/manroff
1) cp include/arpa/nameser.h /usr/include/arpa  
   Also, on ultrix 2.x, if you haven't fixed
   the inet_addr definition in inet.h, do
   cp include/arpa/inet.h /usr/include/arpa
2) cp include/resolv.h /usr/include
3) cp include/netdb.h /usr/include/netdb.h
OR
   cp include/netdb.h.4.2 /usr/include/netdb.h
OR
   edit /usr/include/netdb.h
4) cp man/*.1 /usr/man/manl
   cp man/*.3 /usr/man/man3
   cp man/*.5 /usr/man/man5
   cp man/*.7 /usr/man/man7
   cp man/*.8 /usr/man/man8
5) cd res; make depend;
   make libresolv.a;
   make install
OR
   update the libc sources as in the 4.3BSD instructions above
   and use res/Makefile as a guide for integration
   and omit the RES=-lresolv in the next two steps
OR
   compile the .o files in res according to Makefile,
   then use place those object files in /lib/libc.a (keeping a backup!)
   and omit the RES=-lresolv in the next two steps
6) edit named/pathnames.h to correpond with your system's configuration
7) cd named; make depend; make RES=-lresolv all; make install
   (if your system defines signal-catching routines to return int
   instead of void, use "make DEFINES=-DSIG_FN=int RES=-lresolv all")
8) edit tools/nslookup/pathnames.h to correpond with your system's
     configuration
9) cd tools/nslookup; make RES=-lresolv nslookup install
10) create the master files (samples in conf/master/*)
11) edit /etc/rc.local to include:

if [ -f /etc/named ]; then
        /etc/named; echo -n ' named' >/dev/console
fi

12) eventually, recompile network client and server programs that use
gethostbyname, etc.
@


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 4
a4 4
The official version of BIND is now 8.1.1.  This is 4.9.6, the last of 4.*
which we are releasing since it has some important security bugs fixed.

The official place to get BIND is <URL:ftp://ftp.isc.org/isc/bind/src>.
a9 3
					comp.protocols.dns.bind
					comp.protocols.dns.ops
					comp.protocols.dns.std
d11 11
a21 2
BIND is currently maintained by:	The Internet Software Consortium
					(see <URL:http://www.isc.org/isc>.)
d24 204
@


1.1.1.1.2.2
log
@Update 2.2 from bind 4.9.6 to 4.9.7-t1b
@
text
@d1 2
a2 7
Internet Software Consortium
BIND Release 4.9.7 README
$Date: 1998/04/07 04:24:01 $

The official version of ISC BIND is now 8.1.1.  This is ISC BIND 4.9.7,
hoped to be the last of 4.*, which we are releasing since it has an important
security bug (plus some memory leaks) fixed.
d6 2
a7 2
The official mailing lists are:		<bind-users@@vix.com>	- users/admins
  (use *-request@@* for admin mail)	<bind-workers@@vix.com>	- developers
d9 4
a12 3
The official Usenet newsgroups are:	<URL:news:comp.protocols.dns.bind>
					<URL:news:comp.protocols.dns.ops>
					<URL:news:comp.protocols.dns.std>
d14 2
a15 4
BIND is maintained by:			The Internet Software Consortium
					(see <URL:http://www.isc.org/>)

Bug reports should be sent to:		<bind-bugs@@vix.com>
@


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 4
a4 1
The official place to get BIND is <URL:ftp://ftp.vix.com/pub/bind/release>.
@


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 4
The official version of BIND is now 8.1.1.  This is 4.9.6, the last of 4.*
which we are releasing since it has some important security bugs fixed.

The official place to get BIND is <URL:ftp://ftp.isc.org/isc/bind/src>.
a6 3
					comp.protocols.dns.bind
					comp.protocols.dns.ops
					comp.protocols.dns.std
d8 11
a18 2
BIND is currently maintained by:	The Internet Software Consortium
					(see <URL:http://www.isc.org/isc>.)
d21 204
@


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 2
a2 7
Internet Software Consortium
BIND Release 4.9.7 README
$Date: 1998/04/07 04:24:01 $

The official version of ISC BIND is now 8.1.1.  This is ISC BIND 4.9.7,
hoped to be the last of 4.*, which we are releasing since it has an important
security bug (plus some memory leaks) fixed.
d6 2
a7 2
The official mailing lists are:		<bind-users@@vix.com>	- users/admins
  (use *-request@@* for admin mail)	<bind-workers@@vix.com>	- developers
d9 4
a12 3
The official Usenet newsgroups are:	<URL:news:comp.protocols.dns.bind>
					<URL:news:comp.protocols.dns.ops>
					<URL:news:comp.protocols.dns.std>
d14 2
a15 4
BIND is maintained by:			The Internet Software Consortium
					(see <URL:http://www.isc.org/>)

Bug reports should be sent to:		<bind-bugs@@vix.com>
@


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 75
a75 112
This is the source portion of BIND version 8.1.2-T3B.  Its companions are
"doc" and "contrib" so you are probably not missing anything.

See the CHANGES file for a detailed listing of all changes.  See the INSTALL
file for information on building and installing BIND 8.1.2.


BIND 8.1.2 Highlights

	Security fixes for a number of problems including:

		An attacker could overwrite the stack if inverse query support
		was enabled.

		A number of denial of service attacks where malformed packets
		could cause the server to crash.

		The server was willing to answer queries on its forwarding
		sockets.

	Several memory leaks have been plugged.

	The server no longer panics if a periodic interface scan fails due
	to no file descriptors being available.

	Updates to a number of ports.  New ports for QNX, LynxOS, HP-UX 9.x,
	and HP MPE.

	"limit files unlimited" now works as expected on systems where setting
	an infinite rlim_max for RLIMIT_NOFILE works.

	Adding and deleting the same record in the same dynamic update no
	longer crashes the server.

	If a dynamic update fails, rollback is now done in LIFO order instead
	of FIFO order.

	Better behavior when priming of the root servers fails.

	purge_zone() didn't work correctly for the root zone, allowing
	old data to persist after loading the zone.

	Improved handling of oversized UDP packets.

	All hosts on the also-notify list are now notified.

	The meaning of the count returned by select() varies somewhat by
	operating system, and this could cause previous releases of the
	server to spin.

	Per-host statistics may be disabled by specifying 'host-statistics no'
	in named.conf.

	The maximum number of zones has been increased from 32768 to 65536.

	query-source may specify an address and port that the server is
	already listening on.  BIND 8.1.1 required that either the address
	or port be wild.  E.g., you can now say:

		listen-on port 53 { 10.0.0.1; };
		query-source address 10.0.0.1 port 53;

	The value of FD_SETSIZE to use may be specified.

	Experimental -u (set user id), -g (set group id), and -t (chroot)
	command line options.  See the INSTALL file for details.


BIND 8 Features

	-> DNS Dynamic Updates (RFC 2136)

	-> DNS Change Notification (RFC 1996)

	-> Completely new configuration syntax

	-> Flexible, categorized logging system

	-> IP-address-based access control for queries, zone transfers, and
	   updates that may be specified on a zone-by-zone basis

	-> More efficient zone transfers

	-> Improved performance for servers with thousands of zones

	-> The server no longer forks for outbound zone transfers

	-> Many bug fixes


File and Directory Overview

	CHANGES				history of added features and
					fixed bugs

	INSTALL				how to build and install

	README				this file
						
	TODO				features planned but not yet written

	Version				the version number of this release

	bin/*				source for executables, including
					the nameserver

	include/*			public .h files

	lib/*				the resolver and various BIND
					support libraries

	port/*				ports to various operating systems
d77 200
d278 2
a279 31
Kits, Questions, Comments, and Bug Reports

    <URL:ftp://ftp.isc.org/isc/bind/src/cur>        current non-test release
    <URL:ftp://ftp.isc.org/isc/bind/src/testing>    latest public test kit

    <URL:usenet:comp.protocols.dns.bind>            using BIND
    <URL:usenet:comp.protocols.dns.ops>             DNS operations in general
    <URL:usenet:comp.protocols.dns.std>             DNS standards in general

    <URL:mailto:bind-users-request@@vix.com>         gw'd to u:c.p.d.bind
    <URL:mailto:namedroppers-request@@internic.net>  gw'd to u:c.p.d.std
    <URL:mailto:bind-workers-request@@vix.com>       code warriors only please

    <URL:http://www.isc.org/bind.html>		    the BIND home page
    <URL:mailto:bind-bugs@@isc.org>		    bug reports


To Support the Effort

	Note that BIND is supported by the Internet Software Consortium, and
	although it is free for use and redistribution and incorporation into
	vendor products and export and anything else you can think of, it
	costs money to produce.  That money comes from ISPs, hardware and
	software vendors, companies who make extensive use of the software,
	and generally kind hearted folk such as yourself.

	The Internet Software Consortium has also commissioned a DHCP server
	implementation, has taken over official support/release of the INN
	system, and supports the Kerberos Version 5 effort at MIT.  You can
	learn more about the ISC's goals and accomplishments from the web page
	at <URL:http://www.isc.org/>.
@


1.1.1.6
log
@Import final bind-8.1.2 release.

Obtained from: ftp.isc.org
@
text
@d1 1
a1 1
This is the source portion of BIND version 8.1.2.  Its companions are
d29 1
a29 1
	"files unlimited" now works as expected on systems where setting
@


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 2
a2 2
This is the source portion of BIND version 8.2.2, Patchlevel 5.  Its
companions are "doc" and "contrib" so you are probably not missing anything.
d5 1
a5 69
file for information on building and installing BIND.

See the SUPPORT file for information on obtaining commercial support for ISC
artifacts including BIND, INN, and DHCP.

SECURITY NOTE:

	Solaris and other pre-4.4BSD kernels do not respect ownership or
	protections on UNIX-domain sockets.  This means that the default
	path for the NDC control socket (/var/run/ndc) is such that any
	user (root or other) on such systems can issue any NDC command
	except "start" and "restart".  The short term fix for this is to
	override the default path and put such control sockets into root-
	owned directories which do not permit non-root to r/w/x through them.
	The medium term fix is for BIND to enforce this requirement internally.
	The long term fix is for all kernels to upgrade to 4.4BSD semantics.

BIND 8.2.2 patchlevel 5 Highlights

	Bug in named-xfer (from patchlevel 4).
	Portability to IPv6 versions of FreeBSD, OpenBSD, NetBSD.
	Portability improvements (A/UX, AIX, IRIX, NetBSD, SCO, MPE/IX, NT).
	"also-notify" option could cause memory allocation errors.
	IXFR improvements (though client-side is still disabled).
	Contributed software upgraded (including TIS's "dns_signer").
	Several latent denial-of-service bugs fixed (from audits, not abuse).
	New "make noesw" top-level target for removing encumbered components.

BIND 8.2.2 Highlights

	Interoperability with MS-Win2K has been improved.                     
	Server-side IXFR is now known to work even under high load.                 
	Support for Windows/NT (thanks to BayNetworks).
	More fixes, especially to DNSSEC, TSIG, IXFR, and selective forwarding.
	More portability improvements and lint removal (A/UX 3.1.1, SCO 5.0).
	Better NOTIFY behaviour, especially with large update volume.
	Better UPDATE handling, including SRV RR support and RFC compliance.
	Fix for "ndc reload ZONENAME" (specific zone reload) problems.
	Fix for round robin when multiple CNAMEs are in use.
	New "min-roots" (MINROOTS) and "serial-queries" (MAXQSERIAL) options.
	Log files are no longer auto-rotated every time the server starts up.
	New "ndc reconfig" command only finds new/deleted zones, no stat()ing.
	New global options for "transfer-source" and "also-notify".
	$GENERATE now supports more record types, and options.


BIND 8.2.1 Highlights

	Bug fixes, especially to DNSSEC, TSIG, IXFR, and selective forwarding.
	Portability improvements and lint removal.
	Use best SOA rather than first-better when selecting an AXFR master.
	$TTL now accepts symbolic time values (such as "$TTL 1h30m").
	"ndc reload" now accepts a zone argument, for single-zone reloads.
	ndc is better behaved; is verbose or quiet when appropriate.
	event and error reporting improvements.

BIND 8.2 Highlights

	RFC 2308 (Negative Caching)
	RFC 2181 (DNS Clarifications)
	RFC 2065 (DNS Security)
	TSIG (Transaction SIGnatures)
	support for multiple virtual name servers
	NDC uses a "control channel" now (no more signals)
	"Split DNS" via zone type "forward".

	Many bug fixes
	Documentation improvements
	Performance enhancements
@


1.1.1.6.2.2
log
@Update to BIND 8.2.2-P7 which fixes some bugs as well as some security
problems.

This fixes the ZXFR DoS attack.
@
text
@d1 1
a1 1
This is the source portion of BIND version 8.2.2, Patchlevel 7.  Its
@


1.1.1.6.2.3
log
@MFC:	8.2.3
@
text
@d1 2
a2 2
This is the source portion of BIND version 8.  Its companions are "doc" and
"contrib" so you are probably not missing anything.
d10 1
a10 2
Note that BIND 8 is in "end-of-life", having been replaced by BIND 9.  See
http://www.isc.org/ for more details.
d12 9
a20 10
BIND 8.2.3 Highlights

	Improved support for Windows NT and Windows 2000.
	Host stats are no longer required to track the source of a record.
	IXFR improvements.
	Forwarders track and use RTT to select fastest.
	Unix domain sockets implementions that require the directory
	to be secure, are now secured.
	Many minor problems fixed.
	Linux DoS removed.
d50 1
d75 1
d136 1
d158 1
d199 1
d211 3
a213 3
	system, and has supported the Kerberos Version 5 effort at MIT.  You
	can learn more about the ISC's goals and accomplishments from the web
	page at <URL:http://www.isc.org/>.
@


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 2
a2 2
This is the source portion of BIND version 8.2.2, Patchlevel 5.  Its
companions are "doc" and "contrib" so you are probably not missing anything.
d5 1
a5 69
file for information on building and installing BIND.

See the SUPPORT file for information on obtaining commercial support for ISC
artifacts including BIND, INN, and DHCP.

SECURITY NOTE:

	Solaris and other pre-4.4BSD kernels do not respect ownership or
	protections on UNIX-domain sockets.  This means that the default
	path for the NDC control socket (/var/run/ndc) is such that any
	user (root or other) on such systems can issue any NDC command
	except "start" and "restart".  The short term fix for this is to
	override the default path and put such control sockets into root-
	owned directories which do not permit non-root to r/w/x through them.
	The medium term fix is for BIND to enforce this requirement internally.
	The long term fix is for all kernels to upgrade to 4.4BSD semantics.

BIND 8.2.2 patchlevel 5 Highlights

	Bug in named-xfer (from patchlevel 4).
	Portability to IPv6 versions of FreeBSD, OpenBSD, NetBSD.
	Portability improvements (A/UX, AIX, IRIX, NetBSD, SCO, MPE/IX, NT).
	"also-notify" option could cause memory allocation errors.
	IXFR improvements (though client-side is still disabled).
	Contributed software upgraded (including TIS's "dns_signer").
	Several latent denial-of-service bugs fixed (from audits, not abuse).
	New "make noesw" top-level target for removing encumbered components.

BIND 8.2.2 Highlights

	Interoperability with MS-Win2K has been improved.                     
	Server-side IXFR is now known to work even under high load.                 
	Support for Windows/NT (thanks to BayNetworks).
	More fixes, especially to DNSSEC, TSIG, IXFR, and selective forwarding.
	More portability improvements and lint removal (A/UX 3.1.1, SCO 5.0).
	Better NOTIFY behaviour, especially with large update volume.
	Better UPDATE handling, including SRV RR support and RFC compliance.
	Fix for "ndc reload ZONENAME" (specific zone reload) problems.
	Fix for round robin when multiple CNAMEs are in use.
	New "min-roots" (MINROOTS) and "serial-queries" (MAXQSERIAL) options.
	Log files are no longer auto-rotated every time the server starts up.
	New "ndc reconfig" command only finds new/deleted zones, no stat()ing.
	New global options for "transfer-source" and "also-notify".
	$GENERATE now supports more record types, and options.


BIND 8.2.1 Highlights

	Bug fixes, especially to DNSSEC, TSIG, IXFR, and selective forwarding.
	Portability improvements and lint removal.
	Use best SOA rather than first-better when selecting an AXFR master.
	$TTL now accepts symbolic time values (such as "$TTL 1h30m").
	"ndc reload" now accepts a zone argument, for single-zone reloads.
	ndc is better behaved; is verbose or quiet when appropriate.
	event and error reporting improvements.

BIND 8.2 Highlights

	RFC 2308 (Negative Caching)
	RFC 2181 (DNS Clarifications)
	RFC 2065 (DNS Security)
	TSIG (Transaction SIGnatures)
	support for multiple virtual name servers
	NDC uses a "control channel" now (no more signals)
	"Split DNS" via zone type "forward".

	Many bug fixes
	Documentation improvements
	Performance enhancements
@


1.1.1.7.2.1
log
@MFC: bind 8.2.3-T5B
@
text
@d1 2
a2 2
This is the source portion of BIND version 8.2.3-T2B.  Its companions 
are "doc" and "contrib" so you are probably not missing anything.
d211 3
a213 3
	system, and has supported the Kerberos Version 5 effort at MIT.  You
	can learn more about the ISC's goals and accomplishments from the web
	page at <URL:http://www.isc.org/>.
@


1.1.1.7.2.2
log
@MFC:	BIND 8.2.3
@
text
@d1 2
a2 2
This is the source portion of BIND version 8.  Its companions are "doc" and
"contrib" so you are probably not missing anything.
d10 1
a10 2
Note that BIND 8 is in "end-of-life", having been replaced by BIND 9.  See
http://www.isc.org/ for more details.
d12 9
a20 10
BIND 8.2.3 Highlights

	Improved support for Windows NT and Windows 2000.
	Host stats are no longer required to track the source of a record.
	IXFR improvements.
	Forwarders track and use RTT to select fastest.
	Unix domain sockets implementions that require the directory
	to be secure, are now secured.
	Many minor problems fixed.
	Linux DoS removed.
d50 1
d75 1
d136 1
d158 1
d198 1
@


1.1.1.7.2.3
log
@Fix conflicts after MFC of BIND 8.2.4.
@
text
@a12 15
BIND 8.2.4 Highlights
	NSAP processing was not RFC 1706 compliant. NOTE: OLD MASTER FILES
	NEED TO BE CORRECTED (0x added to NSAP) AND CACHE FILES REMOVED.
	Fixes long-standing protocol incompatibility in DNSSEC support.
	Avoids fwd'ing to root name servers if response will be rejected.
	new port/cygwin contributed by s_c_biggs@@bigfoot.com.
	new contrib/mdnkit (V1.3) from author.
	new contrib/adm from official ftp site.
	new contrib/host from author.
	new contrib/dnsp from author.
	fixed file descriptor leak in resolver.
	fixed a major memory leak in the processing of dynamic updates.
	numerous portability improvements.
	numerous bug fixes.

@


1.1.1.7.2.3.2.1
log
@Upgrade to version 8.3.3.

Approved by:	security-officer
@
text
@a12 22
BIND 8.3.3 Highlights
	Security Fix libbind. All applications linked against libbind
	need to relinked.
	'rndc restart' now preserves named's arguements

BIND 8.3.2 Highlights
	dig, nslookup, host and nsupdate have improved IPv6 support.

BIND 8.3.1 Highlights
	Critical bug fix to prevent DNS storms. If you have BIND 8.3.0 you
	need to upgrade.

BIND 8.3.0 Highlights
	IPv6 transport support in resolver (from KAME).
	Opaque rdata support.
	EDNS0 support.
	Glue ordering to help non-ENDS0 aware clients (servers) cope with
	larger responses as a result of IPv6 by allowing A records to be added
	first to the additional section.  IPv6 capable clients are expected to
	use EDNS0 to allow larger responses to be sent.
	Bug Fixes, includes BIND 8.2.5 changes.

d15 1
a15 1
	NEED TO BE CORRECTED AND CACHE FILES REMOVED.
@


1.1.1.7.2.3.4.1
log
@Upgrade to version 8.3.3.

Approved by:	security-officer
@
text
@a12 22
BIND 8.3.3 Highlights
	Security Fix libbind. All applications linked against libbind
	need to relinked.
	'rndc restart' now preserves named's arguements

BIND 8.3.2 Highlights
	dig, nslookup, host and nsupdate have improved IPv6 support.

BIND 8.3.1 Highlights
	Critical bug fix to prevent DNS storms. If you have BIND 8.3.0 you
	need to upgrade.

BIND 8.3.0 Highlights
	IPv6 transport support in resolver (from KAME).
	Opaque rdata support.
	EDNS0 support.
	Glue ordering to help non-ENDS0 aware clients (servers) cope with
	larger responses as a result of IPv6 by allowing A records to be added
	first to the additional section.  IPv6 capable clients are expected to
	use EDNS0 to allow larger responses to be sent.
	Bug Fixes, includes BIND 8.2.5 changes.

d15 1
a15 1
	NEED TO BE CORRECTED AND CACHE FILES REMOVED.
@


1.1.1.7.2.4
log
@MFC: ISC BIND 8.3.1-REL.
@
text
@a12 14
BIND 8.3.1 Highlights
	Critical bug fix to prevent DNS storms. If you have BIND 8.3.0 you
	need to upgrade.

BIND 8.3.0 Highlights
	IPv6 transport support in resolver (from KAME).
	Opaque rdata support.
	EDNS0 support.
	Glue ordering to help non-ENDS0 aware clients (servers) cope with
	larger responses as a result of IPv6 by allowing A records to be added
	first to the additional section.  IPv6 capable clients are expected to
	use EDNS0 to allow larger responses to be sent.
	Bug Fixes, includes BIND 8.2.5 changes.

d15 1
a15 1
	NEED TO BE CORRECTED AND CACHE FILES REMOVED.
@


1.1.1.7.2.5
log
@MFC: Import of ISC BIND 8.3.2-T1B.

Approved by:	brian (re)
@
text
@a12 3
BIND 8.3.2 Highlights
	dig, nslookup, host and nsupdate have improved IPv6 support.

@


1.1.1.7.2.5.2.1
log
@Upgrade BIND to version 8.3.3.

Approved by:	security-officer
@
text
@a12 5
BIND 8.3.3 Highlights
	Security Fix libbind. All applications linked against libbind
	need to relinked.
	'rndc restart' now preserves named's arguements

@


1.1.1.7.2.6
log
@MFC of version 8.3.3 import
@
text
@a12 5
BIND 8.3.3 Highlights
	Security Fix libbind. All applications linked against libbind
	need to relinked.
	'rndc restart' now preserves named's arguements

@


1.1.1.7.2.7
log
@MFC of version 8.3.4 import
@
text
@a12 3
BIND 8.3.4 Highlights
	Security Fix DoS and buffer overrun.

@


1.1.1.7.2.8
log
@MFC of version 8.3.6 import
@
text
@a12 6
BIND 8.3.6 Highlights
	Maintenance release.

BIND 8.3.5 Highlights
	Maintenance release.

@


1.1.1.7.2.9
log
@MFC of version 8.3.7 import

Requested by:	security-officer
@
text
@a12 3
BIND 8.3.7 Highlights
	Security release.

@


1.1.1.8
log
@Virgin import of BIND v8.2.3-T5B
@
text
@d1 2
a2 2
This is the source portion of BIND version 8.2.3-T2B.  Its companions 
are "doc" and "contrib" so you are probably not missing anything.
d211 3
a213 3
	system, and has supported the Kerberos Version 5 effort at MIT.  You
	can learn more about the ISC's goals and accomplishments from the web
	page at <URL:http://www.isc.org/>.
@


1.1.1.9
log
@Virgin import of BIND v8.2.3-REL
@
text
@d1 2
a2 2
This is the source portion of BIND version 8.  Its companions are "doc" and
"contrib" so you are probably not missing anything.
d10 1
a10 2
Note that BIND 8 is in "end-of-life", having been replaced by BIND 9.  See
http://www.isc.org/ for more details.
d12 9
a20 10
BIND 8.2.3 Highlights

	Improved support for Windows NT and Windows 2000.
	Host stats are no longer required to track the source of a record.
	IXFR improvements.
	Forwarders track and use RTT to select fastest.
	Unix domain sockets implementions that require the directory
	to be secure, are now secured.
	Many minor problems fixed.
	Linux DoS removed.
d50 1
d75 1
d136 1
d158 1
d198 1
@


1.1.1.10
log
@Virgin import of BIND v8.2.4-REL
@
text
@a12 15
BIND 8.2.4 Highlights
	NSAP processing was not RFC 1706 compliant. NOTE: OLD MASTER FILES
	NEED TO BE CORRECTED (0x added to NSAP) AND CACHE FILES REMOVED.
	Fixes long-standing protocol incompatibility in DNSSEC support.
	Avoids fwd'ing to root name servers if response will be rejected.
	new port/cygwin contributed by s_c_biggs@@bigfoot.com.
	new contrib/mdnkit (V1.3) from author.
	new contrib/adm from official ftp site.
	new contrib/host from author.
	new contrib/dnsp from author.
	fixed file descriptor leak in resolver.
	fixed a major memory leak in the processing of dynamic updates.
	numerous portability improvements.
	numerous bug fixes.

@


1.1.1.11
log
@Import of ISC BIND 8.3.1-REL.
@
text
@a12 14
BIND 8.3.1 Highlights
	Critical bug fix to prevent DNS storms. If you have BIND 8.3.0 you
	need to upgrade.

BIND 8.3.0 Highlights
	IPv6 transport support in resolver (from KAME).
	Opaque rdata support.
	EDNS0 support.
	Glue ordering to help non-ENDS0 aware clients (servers) cope with
	larger responses as a result of IPv6 by allowing A records to be added
	first to the additional section.  IPv6 capable clients are expected to
	use EDNS0 to allow larger responses to be sent.
	Bug Fixes, includes BIND 8.2.5 changes.

d15 1
a15 1
	NEED TO BE CORRECTED AND CACHE FILES REMOVED.
@


1.1.1.12
log
@Import of ISC BIND 8.3.2-T1B.
@
text
@a12 3
BIND 8.3.2 Highlights
	dig, nslookup, host and nsupdate have improved IPv6 support.

@


1.1.1.13
log
@Import of ISC BIND version 8.3.3
@
text
@a12 5
BIND 8.3.3 Highlights
	Security Fix libbind. All applications linked against libbind
	need to relinked.
	'rndc restart' now preserves named's arguements

@


1.1.1.14
log
@Import of ISC BIND version 8.3.4
@
text
@a12 3
BIND 8.3.4 Highlights
	Security Fix DoS and buffer overrun.

@


1.1.1.15
log
@Import of ISC BIND version 8.3.6.

Version 8.3.5 was skipped due to bugs fixed in this version.
@
text
@a12 6
BIND 8.3.6 Highlights
	Maintenance release.

BIND 8.3.5 Highlights
	Maintenance release.

@


1.1.1.16
log
@Import of ISC BIND version 8.3.7

Approved by:	re
Requested by:	security-officer
@
text
@a12 3
BIND 8.3.7 Highlights
	Security release.

@


1.1.1.16.4.1
log
@MFC: BIND 9 and related bits.

Approved by:	re
@
text
@@


