From owner-freebsd-current Mon Aug 4 10:45:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA15204 for current-outgoing; Mon, 4 Aug 1997 10:45:19 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA15197 for ; Mon, 4 Aug 1997 10:45:16 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA04371; Mon, 4 Aug 1997 10:43:11 -0700 From: Terry Lambert Message-Id: <199708041743.KAA04371@phaeton.artisoft.com> Subject: Re: Moving to a more current BIND To: Studded@dal.net Date: Mon, 4 Aug 1997 10:43:11 -0700 (MST) Cc: karl@Mcs.Net, freebsd-current@FreeBSD.ORG, lists@tar.com, terry@lambert.org In-Reply-To: <199708040518.WAA29255@mail.san.rr.com> from "Studded" at Aug 3, 97 10:17:57 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Using CNAMEs in NS lines is in violation of the BIND rules and will break. > > It is a violation of the spec, but it will also work. Just for > fun, I added an ns record for a cname. From an 8.1.1 system to another, > and from a 4.9.6 system nslookup specifying the cnamed server worked fine. > I don't use this feature myself, but I know others that do (with 8.1.1 > systems) and it works. That doesn't mean it's a good idea. In the future > compatability for this could end. > > For the details on why this is bad, see the BIND FAQ, > /usr/src/contrib/bind/doc/misc/FAQ.2of2 Question 6.6. In the future, I will have more hardware and the problem will silently disappear. I was only complaining that bind complains to other people to get them to brow-beat me, yet then proceeds to work. Better that it complain to me, and let me ignore it. Yes, at my peril. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.