how to setup class b ?

[Michael Voight]

Do you want a different name for each address?
Then you need:

1.o in ptr host1.my.com
2.0 in ptr host2.my.com
3.0 in ptr host3.my.com
4.0 in ptr host4.my.com

etc for the 0 subnet

then 

1.1
2.1
3.1 
etc

for the 1 subnet

If you are converting from a hosts file, h2n utility will create both
the forward and reverse zones.
There is no difference between an B or C zone file except when not
typing the full ptr name and allowing it to append the reverse zone name
to the entry. Since a ptr record contains the address in reverse order,
then if you are entering 2 numbers in the address, they will be in
reverse order.

Michael

Daniel Wittenberg wrote:
> 
> Maybe this would be easier:
> Is there documentation somewhere on how to setup 1 table for the reverse on an
> entire class B?  Or maybe 2 tables, but I just don't want 1 table for each /24
> net...too many tables...
> I didn't find anything usefull in the o'riley dns & bind book, so if there is
> another book or web site or something..
> 
> Dan
> 
> Michael Voight wrote:
> >
> > Daniel Wittenberg wrote:
> > >
> > > ok...this doesn't make a lot of sense then.  The address I have is say
> > > 172.27.0.0, so the table is for 172.27, so that is why I had 0.1, 0.2...255.255.
> > >  The 1.0 and 2.0 are completely different net's in this case.  I basically have
> > > set aside the first class C of addresses for server use, and the rest are DHCP.
> > > Does this make more sense?  So the addresses that do not work:
> > > 172.27.0.1
> > > 172.27.0.2
> > > 172.27.0.x
> > >
> > > 172.27.1.x does work...just not 0.x as I unsuccessfully tried to state earlier...
> > >
> > > Dan
> >
> > Dan,
> >
> > Then, give us the full info from the zone. Your posting did not include
> > any PTR entries for the 0 subnet, so we assumed 0.1 and 0.2 were what
> > you were trying to use. Since this is a reverse zone, 0.1 would mean
> > 172.27.1.0.
> >
> > Michael