CentOS - Feb 2007 - default Bind on CentOS 4.4 and reverse DNS subnets issue?

Anybody knows if the Bind version on CentOS 4.4 (9.2.4) has issues with 
doing reverse DNS for subnets? (networks smaller than /24)

I keep a reverse DNS /26 subnet on Bind 9.3.1 (Fedora) and it works fine.
I've a /27 subnet on CentOS 4 (bind 9.2.4), exactly the same config just 
different subnets and addresses, and it does not work. I do a "dig 
@localhost .......in-addr.arpa. PTR" and there's no ANSWER section. The
logs provide no clues, all zones load up clean.

Identical config, different behavior. Maximum frustration. :-/

-- 
Florin Andrei

http://florin.myip.org/

On Wed, February 28, 2007 2:26 pm, Florin Andrei wrote:
> Anybody knows if the Bind version on CentOS 4.4 (9.2.4) has issues with
> doing reverse DNS for subnets? (networks smaller than /24)
>
> I keep a reverse DNS /26 subnet on Bind 9.3.1 (Fedora) and it works fine.
> I've a /27 subnet on CentOS 4 (bind 9.2.4), exactly the same config
just
> different subnets and addresses, and it does not work. I do a "dig
> @localhost .......in-addr.arpa. PTR" and there's no ANSWER
section. The
> logs provide no clues, all zones load up clean.
>
> Identical config, different behavior. Maximum frustration. :-/
I'm not aware of any issues.  Can you shows us the portion of named.conf
for that zone file and the zone file.

Thanks!

-- 
Matthew Martz
CentOS Mirror Admin
mdmartz at gflug.net

On Wed, 28 Feb 2007, Florin Andrei wrote:
> Anybody knows if the Bind version on CentOS 4.4 (9.2.4) has issues with
doing
> reverse DNS for subnets? (networks smaller than /24)
>
> I keep a reverse DNS /26 subnet on Bind 9.3.1 (Fedora) and it works 
> fine. I've a /27 subnet on CentOS 4 (bind 9.2.4), exactly the same 
> config just different subnets and addresses, and it does not work. I 
> do a "dig @localhost .......in-addr.arpa. PTR" and there's no
ANSWER
> section. The logs provide no clues, all zones load up clean.
>
> Identical config, different behavior. Maximum frustration. :-/
I don't have any subnets smaller than /24, but here's what I'd do to
test it. Assuming that 10.1.1.1 is in your address range,

   dig +noall +authority -x 10.1.1.1 SOA

If you're on a host allowed to do DNS transfers, you can try grabbing 
the entire subnet:

   dig $(dig +noall +authority -x 10.1.1.1 SOA | awk '{print $1}') AXFR

-- 
Paul Heinlein <> heinlein at madboa.com <> www.madboa.com