Hi all, sorry for being late for this summary, but I had to read a lot
to find the answer. First thanks to:
    Jeff Higgins <HIGGINS_at_aces.k12.ct.us> ACES Technology 	         
Services Hamden, CT USA
and
        Daniel E. Visbal <daniel_at_ds5200.sistecol.com> STA Colombia
My original post was:
 
> Hi everybody, I am trying to configure a secondary server for a network
> that it is masked, but I am not sure how to do this in a secure way, I
> did this:
> 
> in named.boot:
> 
> secondary   companydomain.com xx.yy.zz.vv  hosts.company
> secondary   ww.zz.yy.xx.in-addr.arpa xx.yy.zz.vv  hosts.company.rev
> 
> where xx.yy.zz.vv is the ip of the DNS server, and xx.yy.zz.ww is the
> real address for the network, and the mask is something like
> 255.255.255.240.
> 
> Thanks in advance for everybody,
> 
> Leonardo Mosquera
> System Manager
> Internet Telecom
> Colombia
And the answer was to delegate down to the fourth octet of IP class C
address, so you will have one domain per IP address. Better look the
example I took from a good FAQ dns document edited and maintained by
Chris Peckham in this address: 
ftp://ftp.njit.edu/pub/dns/cptd.faq
Thanks to you too Chris!!!!!:
  Take as an example the net 192.1.1.x, and example subnet mask 
   255.255.255.240.
 
   We first define the domain for the class C net,
 
$origin  1.1.192.in-addr.arpa
_at_       SOA   (usual stuff)
_at_       ns  some.nameserver
        ns  some.other.nameserver
; delegate a subdomain
one     ns  one.nameserver
        ns  some.nameserver
; delegate another
two     ns  two.nameserver
        ns  some.nameserver
; CNAME pointers to subdomain one
0       CNAME 0.one
1       CNAME 1.one
;    through
15      CNAME 15.one
; CNAME pointers to subdomain two
16      CNAME 16.two
17      CNAME 17.two
31      CNAME 31.two
; CNAME as many as required.
 
 
   Now, in the delegated nameserver, one.nameserver
 
$origin one.1.1.192.in-addr.arpa
_at_       SOA (usual stuff)
        NS  one.nameserver
        NS  some.nameserver   ;  secondary for us
0       PTR  onenet.one.domain
1       PTR  onehost.one.domain
;   through
15      PTR  lasthost.one.domain
   And similar for the two.1.1.192.in-addr.arpa delegated domain.
More information about DNS and how it works can be found here:
http://rs.internic.net/nic-support/nicnews/apr97/dns.html
http://www.ludd.luth.se/~kavli/BIND-FAQ.html
and in the books:
TCP/IP Network administration by Craig Hunt
DNS and BIND by Albitz & Liu from O'Reilly & Associates
Again thanks and sorry for this late summary.
Leonardo Mosquera
System Manager
Internet Telecom
Colombia
Received on Wed Oct 08 1997 - 19:57:07 NZDT