[nsd-users] Setting up Reverse DNS Delegation

[Lew Payne]

Hello fellow nsd users,

I'm trying to set up reverse zones in nsd for the netblock I've been
delegated.  I'm having trouble getting it to work, and I'm not sure
why.  I've done this on bind many times before.  So, at this point,
I'm trying to determine if the problem is on my end, or the delegation
(ISP's) end.  Would someone mind walking me through the steps to get
this running on nsd (and/or to debug the delegator).

What I find strange is that I've been asked to allow AXFR from one of
their DNS servers (I guess it's going to secondary my PTR's... but
why?), and to include it (the NS record for their server) in my
reverse zone file.  I've never had to do this before, so maybe someone
on here can give me hints as to how to do this correctly.  Here's what
I've done (provide-xfr IP's mangled for security reasons):

RFC-2317 (e.g., 0/27.3.168.192.in-addr.arpa)  <<-- verified with ISP
that's how they're providing them.

##  REVERSE DNS ZONE
##
zone:
  name: "192/26.187.206.74.in-addr.arpa"
  zonefile: db.192-255.187.206.74.rev
  provide-xfr: 24.456.879.932/26 intrakey
  provide-xfr: 74.96.313.32 interkey  <<== told by ISP to allow AXFR from them!

The file db.192-255.187.206.74.in-addr.arpa contains (abbreviated):
  $ORIGIN 192/26.187.206.74.in-addr.arpa.
  IN NS  ns1.ispserver.com.
  IN NS  ns1.myzoneserver.com.
  IN NS  ns2.myzoneserver.com.
  194   IN      PTR     194.187.206.74.ispserver.com.   <<== told by
ISP to add this!
  ... my stuff... IN PTR

Can someone clue me in as to what I've done wrong...  I suspect I
can't do this plain-old "bind" style.

Regards,
Lew Payne