From owner-freebsd-isp Sat May 13 14:34:59 2000 Delivered-To: freebsd-isp@freebsd.org Received: from juice.shallow.net (node16229.a2000.nl [24.132.98.41]) by hub.freebsd.org (Postfix) with ESMTP id 66DFF37BB2F for ; Sat, 13 May 2000 14:34:56 -0700 (PDT) (envelope-from joshua@roughtrade.net) Received: from localhost (joshua@localhost) by juice.shallow.net (8.9.3/8.9.3) with ESMTP id XAA89734; Sat, 13 May 2000 23:35:49 +0200 (CEST) (envelope-from joshua@roughtrade.net) Date: Sat, 13 May 2000 23:35:49 +0200 (CEST) From: Joshua Goodall To: chip@chocobo.cx Cc: freebsd-isp@FreeBSD.ORG Subject: Re: classless in-addr.arpa In-Reply-To: <20000510143503.A51587@setzer.chocobo.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 10 May 2000, Chip Marshall wrote: > I've found AT&T at least like to use / instead of - in the rev name, > so it end up looking like 128/26.254.181.205.IN-ADDR.ARPA instead. RFC2317, which defines classless reverse delegation, uses forwardslash for examples and then advises readers not to do so, which is a little disingenuous and seems to be mostly for the purpose of annoying the RFC952 pedants with the "Aa-haha! It's NOT A HOSTNAME!" taunt rather than actually using appropriate syntax. Still, it's worth reading. I have seen interoperability tests confirm that a slash is okay even for NT's DNS server & resolver. Be warned that RFC2317, if misconfigured, can result in the customer polluting external caching resolvers with incorrect NS records for your octet-boundary zone. This is not a theoretical problem. I suggest always checking a full zone transfer before allowing the final delegation. -- Joshua Goodall IP Systems Engineer - InterXion - www.interxion.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message