how to setup class b ?
Daniel Wittenberg
reserved for special things, like routers, servers, etc. I have the DHCP,
and forward lookups are fine. The problem in the in-addr lookups don't work
for anything in the first class c. My guess is the way I setup the file:
<normal stuff here>
0.1 IN PTR router.company.com
0.2 IN PTR server.company.com
1.1 IN PTR dhcp-1.1.company.com
If I can't use 0.x for the first 255 addresses, how would you set this up?
Thanks,
Dan
Mark_A...@isc.org
> I want to setup a class B of dhcp address, with the first class c being
> reserved for special things, like routers, servers, etc. I have the DHCP,
> and forward lookups are fine. The problem in the in-addr lookups don't work
> for anything in the first class c. My guess is the way I setup the file:
>
> <normal stuff here>
> 0.1 IN PTR router.company.com
> 0.2 IN PTR server.company.com
> 1.1 IN PTR dhcp-1.1.company.com
My guess is that you are not reversing the last two octets.
1.0 IN PTR router.company.com.
2.0 IN PTR server.company.com.
1.1 IN PTR dhcp-1.1.company.com.
Mark
>
> If I can't use 0.x for the first 255 addresses, how would you set this up?
>
> Thanks,
> Dan
>
>
>
>
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
Michael Voight
Daniel Wittenberg wrote:
>
> I want to setup a class B of dhcp address, with the first class c being
> reserved for special things, like routers, servers, etc. I have the DHCP,
> and forward lookups are fine. The problem in the in-addr lookups don't work
> for anything in the first class c. My guess is the way I setup the file:
>
> <normal stuff here>
> 0.1 IN PTR router.company.com
> 0.2 IN PTR server.company.com
> 1.1 IN PTR dhcp-1.1.company.com
>
> If I can't use 0.x for the first 255 addresses, how would you set this up?
>
> Thanks,
> Dan
This is backwards...
For the 0 subnet, the addresses would be:
1.0
2.0
3.0
Michael Voight
Daniel Wittenberg
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
Mark_A...@isc.org wrote:
>
> > I want to setup a class B of dhcp address, with the first class c being
> > reserved for special things, like routers, servers, etc. I have the DHCP,
> > and forward lookups are fine. The problem in the in-addr lookups don't work
> > for anything in the first class c. My guess is the way I setup the file:
> >
> > <normal stuff here>
> > 0.1 IN PTR router.company.com
> > 0.2 IN PTR server.company.com
> > 1.1 IN PTR dhcp-1.1.company.com
>
> My guess is that you are not reversing the last two octets.
>
> 1.0 IN PTR router.company.com.
> 2.0 IN PTR server.company.com.
> 1.1 IN PTR dhcp-1.1.company.com.
>
> Mark
> >
> > If I can't use 0.x for the first 255 addresses, how would you set this up?
> >
> > Thanks,
> > Dan
> >
> >
> >
> >
Michael Voight
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
Daniel Wittenberg
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
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
Mark_A...@isc.org
Is this any clearer?
172.27.X.Y become Y.X (reverse order) in the reverse zone.
Mark
Forward:
$ORIGIN example.
@ IN SOA ns1.example. hostmaster.ns1.example. 1 2 3 4 5
IN NS ns1.example.
IN NS ns2.example.
host1 IN A 172.27.0.1
host2 IN A 172.27.0.2
host3 IN A 172.27.0.3
ns2 IN A 127.27.255.253
ns1 IN A 127.27.255.254
Reverse:
$ORIGIN 27.172.in-addr.arpa.
@ IN SOA ns1.example. hostmaster.ns1.example. 1 2 3 4 5
IN NS ns1.example.
IN NS ns2.example.
1.0 IN PTR host1.example.
2.0 IN PTR host2.example.
3.0 IN PTR host3.example.
253.255 IN PTR ns2.example.
254.255 IN PTR ns1.example.
Barry Margolin
Daniel Wittenberg <daniel-w...@dellmac.com> 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..
There's no special documentation for this because it's no different from
any other reverse domain. All the documentation assumes that network
administrators are able to apply the basic rules of zone file contruction,
and don't need every minor variation explained explicitly.
For the address 172.27.0.1, the PTR record would be:
1.0.27.127.in-addr.arpa. PTR name
Since the default origin for your class B reverse zone file is
27.127.in-addr.arpa, that can be abbreviated by removing the origin suffix
to:
1.0 PTR name
This is the same way any other domain (forward or reverse) is constructed.
--
Barry Margolin, bar...@bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
Joseph S D Yao
> any other reverse domain. All the documentation assumes that network
> administrators are able to apply the basic rules of zone file contruction,
> and don't need every minor variation explained explicitly.
This does seem to be the attitude of a lot of the documentation. It is
reasonable to hope for this level of ability in all users of BIND. I
don't think that it reasonable to expect that the real world will meet
these hopes.
Everyone - how would a BIND Cookbook be accepted? Granted, that's a
very open question, and one would have to assume it was well-written,
correct, and [much like Joy of Cooking] spends time detailing basic
procedures and "ingredients".
Joy of BINDing? Nah. Sounds too kinky.
[If you don't know what I mean about Joy of Cooking, go look at it.
Then try making a few things. ;-)]
--
Joe Yao js...@cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.