I had an issue with using dig to query my reverse lookups so had to
create separate entries in named.conf like:

# Special notation required for internet delegation (e.g. dig -x ...)
#
zone "192/27.84.44.12.IN-ADDR.ARPA" {
type master;
file "arpa.12.44.84";
allow-transfer { watercom; };
allow-query { any; };
};

# Standard notation required for direct lookups (e.g. dig @mydnshost -x
....)
#
zone "84.44.12.IN-ADDR.ARPA" {
type master;
file "arpa.12.44.84";
allow-transfer { watercom; };
allow-query { any; };
};


That is to say for most purposes the first entry worked fine but if I
specified my host to dig the record from it would complain about
84.44.12.in-addr.arpa not found. Notice both records point to the same
arpa zone file.

I don't think you could split them for the latter entry but I didn't
try.


-----Original Message-----
From: bind-users-bounce@isc.org [mailto:bind-users-bounce@isc.org] On
Behalf Of Tomasz Pajor
Sent: Monday, July 28, 2008 8:21 AM
To: bind-users@isc.org
Subject: Re: how to setup revdns for /16 subnet

> On 28.07.08 13:07, Tomasz Pajor wrote:
> > How can I setup a revdns for a /16 subnet?
> > Subnet is split to 1x /17 2x /18.


> what do you mean split? are they 3 different ranges you got from your

RIR or
> is that private subnet


I've got a /16 and it will be split into 3 subnets, and I want to create
a separate revdns zone for each one.

> > Do I need to create a separate zone file for each class
> > (1.1.x.y.in-addr.arpa, 1.10.x.y.in-addr.arpa etc.) or can I create

three
> > zone files for each subnet and place PTR records there?

>
> You can create reverse zone for /16 (b.a.in-addr.arpa) or /24
> (c.b.a.in-addr.arpa). It's easier to mainsain smaller files (256

reverse
> zones for /24) but it's probably easier to register reverse for /16 if
> that's public address space.


That's a public address space.
I found an rfc (http://www.rfc-archive.org/getrfc.php?rfc=4183) i tried
to do as it says but it won't work :/
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
----------------------------------