From owner-freebsd-isp Tue Nov 30 20:21:12 1999 Delivered-To: freebsd-isp@freebsd.org Received: from quaggy.ursine.com (lambda.blueneptune.com [209.133.45.179]) by hub.freebsd.org (Postfix) with ESMTP id 1F62314F25 for ; Tue, 30 Nov 1999 20:21:09 -0800 (PST) (envelope-from fbsd-isp@ursine.com) Received: from michael (lambda.ursine.com [209.133.45.69]) by quaggy.ursine.com (8.9.3/8.9.3) with ESMTP id UAA50162; Tue, 30 Nov 1999 20:21:08 -0800 (PST) Message-ID: <199911302021070860.4497C34D@quaggy.ursine.com> In-Reply-To: <19991130195148.A22082@sneakerz.org> References: <19991130195148.A22082@sneakerz.org> X-Mailer: Calypso Version 3.00.00.13 (2) Date: Tue, 30 Nov 1999 20:21:07 -0800 From: "Michael Bryan" To: "Dave McKay" , freebsd-isp@freebsd.org Subject: Re: Struggling to get in-addr.arpa working Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> zone "8.57.105.216.in-addr.arpa" { > >I don't really have time to explain the whole concept, but one thing I do= know is that that zone is not going to work. You probably need something= like 28.8/57.105.216.in-addr.arpa for your zone entry. Why? I've done exactly that type of setup before, and it worked just fine. Use the network address as the subdomain under which all entries eventually appear. I believe the O'Reily book even gives exactly such an example of delegating a subnet smaller than a /24. Granted, a naming convention that makes it a little more obvious as to what's going on, like "8/28.57.105.216.in-addr.arpa", has some appeal, but I don't think it's strictly necessary. Michael Bryan fbsd-isp@ursine.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message