Re: delegated reverse dns for very small zone

Thanks.
That was too easy.
And they say bind is complicated!
:-)
Ken


Barry Margolin wrote:

> In article <cdmasa$1kuk$1@sf1.isc.org>, Ken A <ka@pacific.net> wrote:
>
>
>>Hello,
>>
>>A bit of a DNS rookie here & I've not run accross this before using bind.
>>
>>Pacbell has delegated the reverse dns to us for 66.127.104.201-206.
>>
>>I need to create a PTR record for mail.ncoinc.org on 66.127.104.202
>>
>>According to
>>http://www.dnsstuff.com/tools/traver....in-addr.arpa&
>>type=PTR
>>ns1.pbi.net says to look to 202.104.127.66.in-addr.ncoinc.org for the
>>answer.
>>
>>We are authoritative for the ncoinc.org domain, but I'm not sure how to
>>add this PTR record to the zone. Should I create a separate reverse file
>>like I would for a full /24 network, or can I combine it in the forward
>>zone file?
>>What should the entry in named.conf look like? Should it this:
>>
>>zone "104.127.66.in-addr.ncoinc.org" {type master; file "ncoinc.org"; };
>>
>>? I'm sure I'm missing some syntax I've not used before.
>>Thanks for any help.
>
>
> You don't need a new zone, these can go in the existing ncoinc.org zone
> file:
>
> 202.104.127.66.in-addr IN PTR hostname
>