Problem with reverse lookup in CIDR delegated domain [file details]

[Jim]

On Thu, 04 Mar 2004 20:13:52 -0500, Kevin Darcy wrote:

> Jim wrote:
[snip]
>>zone "184.182.116.67.in-addr.arpa" {
>>        type master;
>>        file "m/named.67.116.182.184";
>>        notify yes;
>>};
>> 
>>
> Are you going to put a PTR record in that zone sometime?

There are 2 PTR records in there since the beginning.

[snip]
>>named[4364]: transfer of '182.116.67.in-addr.arpa/IN' from 206.13.28.11#53: \
>>             failed while receiving responses: REFUSED 
>>named[4364]: transfer of '182.116.67.in-addr.arpa/IN' from 206.13.29.11#53: \
>>             failed while receiving responses: REFUSED
>>
>>  
>>
> Looks like they're not permitting zone transfers of that zone from your 
> source address. Perhaps you should ask them to do so.

Wasn't sure if it was my configuring or their configuration. Now that
I know, I'll ask them.
 
>>========================
[snip]
> I think you're imputing some magic to the slash notation that simply 
> isn't there. The ns1.pbi.net and ns2.pbi.net servers don't know about 
> any "184/29.182.116.67.in-addr.arpa" zone, so there's no point in trying 
> to be a slave of that zone from them.
> 
>                                                                          
>                                                 - Kevin

Not that it's magic. Simply it's the first time I've done this sort
of DNS config and every document I've been able to find via google
uses this slash notation, even RFC2317 recommends it. So I ask to
learn the answers and the reasons.

Jim

-- 

Quidquid latine dictum sit, altum viditur.