Clarification - Reverse DNS Setup

[originalremfan at gmail.com]

Barry Margolin wrote:
[snip]
>
> This should be:
>
> zone "160/28.61.168.192.in-addr.arpa" {
>
> i.e. the same name as the domain that your ISP told you they're
> delegating to you.  Where did the "162" come from?

The "162" came from me.  It was based on something I read in the Bind
book about subnetting & reverse zones which apparently I misunderstood.
Thanks for the clarification!

>
> > type master;
> > file "db.162.160-28.61.168.192";
> > allow-query { any; };
> > };
> >
> > and the zone file:
> >
> > $ORIGIN 162.160/28.61.168.192.in-addr.arpa.
>
> This origin statement isn't needed, since the default origin is the
zone
> name.  But if you have it, it should be:
>
> $ORIGIN 160/28.61.168.192.in-addr.arpa
>
[snip]

Okay, from what I read I didn't think it was needed, either.  However,
without it, the zone transfer to my slave wasn't working.  I was
getting:

zone 160/28.61.168.192.in-addr.arpa/IN: refresh: unexpected rcode
(SERVFAIL) from master#53

(note that I originally had the zone named as you suggest, before I
started screwing around with it after reading through the book).

Once I added $ORIGIN, the xfer started working.

>
> Correct the above errors and it should work.
>
> You might also want to change the filename to match the corrected
zone
> name, but that's not critical -- filenames are arbitrary.
> 

Again, thanks for the clarification.  I appreciate your help!