Subnet reverse delagation, RFC 2317

[Phil Mayers]

On 29/07/10 10:00, Jukka Pakkanen wrote:
> 29.7.2010 11:29, Phil Mayers kirjoitti:
>> On 07/29/2010 08:58 AM, Jukka Pakkanen wrote:
>>> Doing first time the RFC 2317 style subnet reverse DNS, and have a
>>> problem with recursion.  When doing a query like "dig @ns1.qnet.fi -x
>>> 62.142.217.200" is succeeds from the local network, but outside I get
>>> "recursion requested but not available".  Our /24 reverse zones work
>>
>> It doesn't look like the reverse is deleted to you:
>>
>> $ dig +comm +nocmd +noques +nostat @ns6.sci.fi
>> 25.217.142.62.in-addr.arpa ptr
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35109
>> ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>> ;; WARNING: recursion requested but not available
>>
>> ;; AUTHORITY SECTION:
>> 217.142.62.in-addr.arpa. 3600    IN    SOA    ns3.sci.fi.
>> hostmaster.sci.fi. 1280318067 3600 900 604800 3600
>>
>> i.e. no CNAME records for the sub-/24.
>
>
> What kind of output should I see in that query above?  The subnet we
> should have delegated to us is 62.142.217.128/25.

Sorry, I'm being slightly dumb and getting confused. The zone is 
delegated fine.

As you've spotted, two of the 5 servers are responding (ns5.sci.fi and 
ns3.sci.fi) but the three others (ns[1,2,3].qnet.fi) return "recursion 
needed"

Presumably those servers aren't actually serving the zone correctly. Are 
you using views? If so, do you have the zone statement in all the 
applicable views?