Bind9 - Reverse net /20 mask 255.255.240.0

[Kevin Darcy]

Hospedagem Interjato wrote:
> Hello? I doubt with a setup for Reverse to
> The networks contracted to the AS, here is the problem and attitudes held,
>
>
> I would like obtain information where to set the bind9 to do the reverse of a network
> /20 mask 255.255.240.0 and
>   
That's 16 /24's
> /18 mask 255.255.192.0 
>   
That's 64 /24's
>
> See what we have done, and details of the problem:
>
> Configured to bind to the other side for a network / 20
> (X.X.48.0/20), but it did not work,
> For the resolution of the same and work, divided into various networks / 24,
>
>  Tried on the net, the site of the bind (http://www.isc.org/sw/bind/add-doc.php)
> And in my draft of the course, but not thought much about it,
> 	
> 		
> For configuration I
> Named.conf put in the following way
>
> zone "48-63.168.192.in-addr.arpa" {
>        type master;
>        file "/var/named/48-63.168.192.in-addr.arpa.zone";
> }; 
>
>
> But not satisfied,
> After initial changed to ip / masks and also not satisfied
>
> zone "48-20.168.192.in-addr.arpa" {
>        type master;
>        file "/var/named/48-20.168.192.in-addr.arpa.zone";
> }; 
>
>   
You seem to be assuming that BIND is CIDR-aware and that you can somehow 
encode the CIDR information into the zone name. Neither assumption is 
correct. BIND treats the in-addr.arpa namespace hierarchy the same way 
it treats any other namespace hierarchy and has no knowledge of CIDR.
> And the files of zones are thus:
>
> $TTL    86400
> @       IN      SOA     XXXXXXXXX. root.XXXXX.  (
>                    2008030406 ; Serial
>                    28800      ; Refresh
>                    14400      ; Retry
>                    2592000    ; Expire
>                    86400 )    ; Minimum
>
> @               IN      NS      ns2.XXXXXXX.
> @               IN      NS      ns3.XXXXXXX.
>
> 1.48            IN      PTR     192-168-48-1.cliente.com.br.
> 2.48            IN      PTR     192-168-48-2.cliente.com.br.
> 3.48            IN      PTR     192-168-48-3.cliente.com.br.
> ...
> ...
> ...
> 253.63          IN      PTR     192-168-63-253.cliente.com.br.
> 254.63          IN      PTR     192-168-63-254.cliente.com.br.
> 255.63          IN      PTR     192-168-63-255.cliente.com.br.
>
>
>   
RFC 1918 is really only applicable to delegations smaller than a /24. 
Any netblock equal to or larger than /24 can be delegated normally as 
single or multiple delegations of /24's, /16's, or /8's.

E.g

48.168.192.in-addr.arpa delegated from 168.192.in-addr.arpa
49.168.192.in-addr.arpa delegated from 168.192.in-addr.arpa
50.168.192.in-addr.arpa delegated from 168.192.in-addr.arpa
and so forth, through
63.168.192.in-addr.arpa delegated from 168.192.in-addr.arpa


                                                                         
               - Kevin