From owner-freebsd-stable  Thu Sep 25 17:25:48 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA24488
          for stable-outgoing; Thu, 25 Sep 1997 17:25:48 -0700 (PDT)
Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA24483
          for <freebsd-stable@FreeBSD.ORG>; Thu, 25 Sep 1997 17:25:43 -0700 (PDT)
Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191])
          by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP
	  id RAA10211; Thu, 25 Sep 1997 17:24:35 -0700 (PDT)
Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194])
	by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id RAA12068;
	Thu, 25 Sep 1997 17:24:34 -0700 (PDT)
Received: (from gdonl@localhost)
	by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id RAA19181;
	Thu, 25 Sep 1997 17:24:32 -0700 (PDT)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199709260024.RAA19181@salsa.gv.tsc.tdk.com>
Date: Thu, 25 Sep 1997 17:24:31 -0700
In-Reply-To: Matt Behrens <matt@megaweapon.zigg.com>
       "Re: [Q] 2.2.5 bind release" (Sep 25,  1:15pm)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: Matt Behrens <matt@megaweapon.zigg.com>, Mike Burgett <mburgett@awen.com>
Subject: Re: [Q] 2.2.5 bind release
Cc: "freebsd-stable@freebsd.org" <freebsd-stable@FreeBSD.ORG>
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sep 25,  1:15pm, Matt Behrens wrote:
} Subject: Re: [Q] 2.2.5 bind release
} On Thu, 25 Sep 1997, Mike Burgett wrote:
} 
} > Will 2.2.5 ship with the 4.9.6 or 8.1.1 BIND release?
} 
} I'm 99.9% sure it'll be 4.9.6.  8.1.1 has the strongest nameserver but its
} resolver library is sorely lacking and would probably cause many packages
} to break.

I'd recommend staying with 4.9.6 for now.  There are a couple of bits
of functionality that were changed in or eliminated from the 8.1.1 server.

One change is the secure zone stuff.  In 4.9.x you can put TXT RRs in
the zone file to limit who is allowed to query the zone.  In 8.1.1 this
is done in the config file, so if you upgrade a server to 8.1.1 and you
were relying on this feature, you have to manually add this to the
config file of each server for the zone.

The biggest feature that was removed was the automatic sorting of A RRs
that the server did for local clients.  If you mount a filesystem
from a multi-homed NFS server, this feature would put the local network
address of the NFS server first in the DNS response.  Recent resolvers
have this functionality built in, but if you have any clients using old and
non-upgradable servers, you may be SOL if you upgrade your server to 8.1.1.
I've got a patch to add this feature back to 8.1.1, but I don't know if
it will be integrated into the official source tree.