A complete block?

[Joseph S D Yao]

On Fri, Jun 01, 2001 at 04:16:12PM -0600, Randall Badilla wrote:
> I'm trying to make a named.conf which let me resolv for the complete block
> of address 192.168.X.X.
> *****************
> On my named.conf I have this:
> zone "168.192.in-addr.arpa" in {
>                 type master;
>                 file "mydomain.rev.interno";
>         };
> ******************
> The mydomain.rev.interno file contains:
> @               IN      SOA     xxxxxxxxx. root.xxxxxxxxx.
> (
>                         2001051706      ; Serial Number
>                         10800           ; Refresh
>                         7200            ; Retry
>                         604800          ; Expire
>                         86400           ; ttl
>                 )
> 
>                         IN      NS      xxxxxxx.
> ;
> $INCLUDE /var/named/Interno/1.168.192.in-addr.arpa
> $INCLUDE /var/named/Interno/X.168.192.in-addr.arpa
> $INCLUDE /var/named/Interno/.
> $INCLUDE /var/named/Interno/.
> $INCLUDE /var/named/Interno/.
> $INCLUDE /var/named/Interno/.
> $INCLUDE /var/named/Interno/.
> $INCLUDE /var/named/Interno/.
> $INCLUDE /var/named/Interno/.
> *******************************
> Each x.168.192.in-addr.arpa have the
> IP		IN 	PTR	xxx information.
> Just that record.
> 
> In theory, my statement on named.conf let me do this for all the complete
> blocks. But when I nslookup and ls -d 168.192.in-addr.arpa, the printout
> is very wierd. It seems that only works for the first block of blocks.
> 
> Can anybody help me?  Or I must put a:
> zone "X.168.192.in-addr.arpa" in {
>                 type master;
>                 file "mydomain.rev.X.interno";
>         };
> for every block.?????????? On the named.conf file.
> 
> TIA.
> 
> PD: Yes, I have reviewed the archives without luck.

You've cut a lot that would have helped you.

I trust that you know that all of those $INCLUDEs don't affect the
final outcome.  They just read the text, character for character, of
those files into where the $INCLUDE line had been, as if you had typed
them yourself.  But it does mean that the system will have to open a
lot more files, and that it's possible that you will have to search
more files for data that has an error in it.

After your $TTL statement [which you don't show], your SOA, and your
NSes [you only show one], you just need your PTR records.  Since the
zone only has two of the octets, you will need to have the other two on
the left-hand side of each PTR record.  For instance, if you have:

192.168.20.1	fritos.cesa.co.cr
192.168.14.168	milk.cesa.co.cr
192.168.200.80	yogurt.cesa.co.cr
192.168.1.42	towel.cesa.co.cr

then, after the straight text substitutions done by your $INCLUDEs,
your file should like something like this:

1.20	IN PTR	fritos.cesa.co.cr.
168.14	IN PTR	milk.cesa.co.cr.
80.200	IN PTR	yogurt.cesa.co.cr.
42.1	IN PTR	towel.cesa.co.cr.

Note two things: (1) the last two octets have been reversed, and
(2) there is a dot ('.') following each name.

Hope this helps!

ALTERNATELY ... you could divide the 168.192.in-addr.arpa. zone up into
subdomains, and delegate them.  ;-)  Even to the same machine.

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
OSIS Center Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.