classless in-addr.arpa delegation

[rhalper at my-deja.com]

Hello,
  I appreciate the help supplied to me by those who responded to my last
post.  Your assistance helped me greatly, though I'm still trying to
track down my reverse lookup problems.  My problems are complicated by
the ridiculouos DNS setup of my upstream provider.  The provider who is
delegating a range of IP addresses to me (209.97.92.96-127 &
209.97.93.1-31) has their primary server (ns1.eliasconsulting.com)
running on an NT box with BIND 4.  The secondary nameserver
(ns2.eliasconsulting.com) is a running FreeBSD & BIND 8.  Here's where
it gets wierd.  Because it's a pain to edit files on the NT box, the
secondary nameserver (ns2) is replicating to the primary nameserver
(ns1).  I have determined that the delegation is setup properly on the
secondary nameserver using classless in-addr.arpa delegation.  However,
I'm not sure if it the delegation is setup properly on the NT box
running NT 4.  I have a couple questions about the setup in the
named.boot file.

secondary 92.97.209.in-addr.arpa 209.97.92.3 db.209.97.92
secondary 96-126.92.97.209.in-addr.arpa 209.227.44.2 db.209.97.92.96-126
secondary 93.97.209.in-addr.arpa 209.227.92.3 db.209.97.93
secondary 1-30.93.97.209.in-addr.arpa 209.227.44.2 db.209.97.93.1-30

As you can see the 209.227.44.2 is my master nameserver & 209.97.92.3 is
my upstream provider's secondary namserver (for all intents and purposes
the primary since it is replicating to the master.)  Does BIND 4 support
the classless in-addr.arpa delegation?  Considering the bizarre setup of
my upstream provider should I have primary listed in the named.boot file
for the delegation areas instead of secondary (see above).  This would
certainly be easier if my upstream provider had a more intuitive setup.

Thanks in advance for your help.

Sincerely,
Reuben Halper
reuben at spacelab.net


Sent via Deja.com http://www.deja.com/
Before you buy.