From owner-freebsd-questions Sun Oct 31 13:35: 0 1999 Delivered-To: freebsd-questions@freebsd.org Received: from easystreet01.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (Postfix) with ESMTP id 7242114BC5 for ; Sun, 31 Oct 1999 13:34:52 -0800 (PST) (envelope-from tashchuk@easystreet.com) Received: from easystreet.com (dsl-209-162-218-66.easystreet.com [209.162.218.66]) by easystreet01.easystreet.com (8.9.1/8.9.1) with ESMTP id NAA13282; Sun, 31 Oct 1999 13:31:25 -0800 (PST) Message-ID: <381CB52D.6702C7A3@easystreet.com> Date: Sun, 31 Oct 1999 13:31:25 -0800 From: Bohdan Tashchuk X-Mailer: Mozilla 4.61 [en] (X11; I; BSD/OS 4.0.1 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Ronald F. Guilmette" Cc: freebsd-questions@FreeBSD.ORG Subject: Re: BIND (8.1.2) reverse mapping for RFC 1918 addresses? - Please Help References: <9422.941393515@segfault.monkeys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Ronald F. Guilmette" wrote: > > P.S. More questions: (1) Why was FreeBSD 3.3 distributed with what would > seem to be such an out-of-date named? (2) Why was the named binary that is > being distributed with FreeBSD 3.3 built to use a different default path > for the configuration file from the one that (it seems) ISC recommends? > Does this fall into the category of `annoyingly pointless incompatibilities'? I ran into very similar problems. Bind 8.1.2 was causing timeouts and so I upgraded to 8.2.1. As you point out, the location of the config file is different between what is in FreeBSD 3.3 and what is in the 8.2.1 port. Also, the port itself is a bit of a hassle, because it installs into /usr/local/... and doesn't replace the obsolete Bind binaries. Earlier I had the same problems with FreeBSD 3.2 and so was disappointed that the September release of 3.3 didn't include the newer Bind which was released in June. In fact I was so anxious to fix my Bind problem that I uploaded the ISO disk image as soon as 3.3 came out, to no avail. Since it didn't fix my problem I avoided buying the CD-ROMs, so the upload definitely saved me some money. I don't know how things are in the Linux world, but this same situation was very typical for BSD/OS, the commercial version I used to use. Whenever a new release of BSD/OS came out there would be complaints that the distributed version of some random software was out of date. So FreeBSD is no worse in that respect, and given that the ports mechanism makes updating relatively easy, FreeBSD is IMO better than BSD/OS in regards to current versions. And since so much of FreeBSD is "volunteer", and it's all free, I really can't complain. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message