help wiht classless network and reverse lookups

[Mark.Andrews at nominum.com]

> 
> on 3/20/01 3:24 PM, Mark.Andrews at nominum.com at Mark.Andrews at nominum.com
> wrote:
> > As for '-' vs '/', either is acceptable to ALL versions of
> > ALL nameservers from ALL vendors.  '-' will cause less
> > problems with buggy resolver libraries than '/' will.
> 
> Really?

	Yes.  I have been setting up classless in-addr.arpa delegations
	for years.  I have also been a BIND developer/contributer for
	year.  I have also been active in DNS protocol design for year
	including being a active member of the working group when the
	RFC was drafted.

	You obviously don't fully understand classless in-addr.arpa
	delegation as none of your "tests" involved updating the
	data at the ISP.

	When you changed the zone from '-' to '/' you would have come
	into agreement with what your ISP had set up in the "parent"
	zone.  There is nothing magic about '-' or '/'.

	Mark


> When I use "-" I get problems. Here's our setup. We're using bind 9.1.1rc1
> (Eek... I need to upgrade...) We have 206.53.3.225-254
> 
> named.conf has
>   zone "224/27.3.53.206.in-addr.arpa" {
>     type master;
>     file "master.224.3.53.206.rev";
>     };
> 
> master.224.3.53.206.rev has
> $ORIGIN 224/27.3.53.206.in-addr.arpa.
> $TTL 86400
> @       IN      SOA     hamlet.mprint.com. postmaster.mprint.com. (
>                         2001030901      ; serial number
>                         10800           ; refresh
>                         3600            ; retry
>                         604800          ; expire
>                         86400 )         ; minimum TTL
>                 IN      NS      hamlet.mprint.com.
>                 IN      NS      ns1.oem.net.
> 225             IN      PTR     router.mprint.com.
> 226             IN      PTR     hamlet.mprint.com.
> 227             IN      PTR     ophelia.mprint.com.
> 228             IN      PTR     as1.mprint.com.
> 229             IN      PTR     filemaker.mprint.com.
> ==========================================
> Experiment 1)
> Change named.conf's zone line to
>   zone "225-254.3.53.206.in-addr.arpa" {
> 
> and master.224.3.53.206.rev's Origin line to
> $ORIGIN 225-254.3.53.206.in-addr.arpa.
> 
> I get no error messages during a -HUP, but the dns returns nothing for any
> address except 206.53.3.226 (the dns' address) using both nslookup and dig.
> 
> =========================================
> Experiment 2)
> On a whim, I try substituting the zone field in named.conf with
>     zone "224-27.3.53.206.in-addr.arpa" {
> thinking that maybe, the dash replaces a slash regarding subnet masks...
> Similarly, change the ORIGIN line in the table to
>     $ORIGIN 224-27.3.53.206.in-addr.arpa.
> 
> Again, no error messages are generated during -HUP, and again, only
> 206.53.3.226 returns data using nslookup and dig.
> 
> ==========================================
> Experiment 3 - how we leave it configured)
> In named.conf
>     zone "224/27.3.53.206.in-addr.arpa" {
> In master.224.3.53.206.rev
>     $ORIGIN 224/27.3.53.206.in-addr.arpa.
> And everything works.
> ==========================================
> Admittedly, there are alot of details I'm leaving out.
>     The zone references in named.conf are actually in the view section
> rather than the zone section.
>     I can't tell you much about the configuration our isp has for the
> Class C 206.53.3/24, except that they assure me they are following RFC 2317
>     I have omitted the rest of the named.conf file, assuming I am giving you
> the pertinant sections and that other statements are not coming into play.
>     But as far as I can tell, either
>         '-' and '/' are not interchangible,
>     or
>         I'm making a mistake in my usage of '-'
> 
> --
> Peter John Anton         Technical Manager, MicroPRINT
> Waltham, Mass., USA               781-890-7500
> peter at mprint.com
> 
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com