not authoritative

[Kevin Darcy]

If you only want to use the range privately, then you'd probably be best off
using one of the RFC 1918 ranges such as 10/8 or 192.168/16, instead of the
range Verio delegated to you. In that case, just set up 10.in-addr.arpa or
168.192.in-addr.arpa on your nameserver and add the relevant PTR records.

If and when it comes time to manage reverse records for your *external* boxes,
then that address range from Verio might come in handy. But you'll have to talk
to Verio about how to delegate it, either by delegating a zone for each
individual address in the range, or using the RFC 2317 (aliasing) technique.
Since they own the parent (/24) domain, they get to choose how they want to
delegate.


- Kevin

Steven Fagan wrote:

> I have only a partial class C from Verio.  I am not looking to make it
> available to the world, just local users.  Verio was nice enough to refer me
> to the makers of my router (I have no idea why).  All I want to do is run a
> local DNS for local users with a reverse lookup.  Do I have to go to a
> 10.xx.xx.xx network to do that?
>
> Thanks for the Help
> Steve
>
> -----Original Message-----
> From: Barry Margolin [mailto:barmar at genuity.net]
> Sent: Friday, January 12, 2001 1:55 PM
> To: comp-protocols-dns-bind at moderators.isc.org
> Subject: Re: not authoritative
>
> In article <93nm83$hvm at pub3.rc.vix.com>,
> Steven Fagan  <SFagan at evokesoft.com> wrote:
> >
> >I have a partial class C from Verio here in Austin, TX.  I want to setup a
> >my own internal DNS.  I have everything but the reverse lookup working
> fine.
> >When I try the reverse lookup it says xx.xx.xx.xx not authoritative for
> >xx.xx.xxin-addr.arpa.  Is there a easy way around this.  I do not want to
> >have to get Verio involved if I can help it.
>
> Is xx.xx.xx.in-addr.arpa the reverse domain for the class C that you have
> part of?  You're not supposed to be authoritative for the whole class C
> reverse domain, Verio is.
>
> Verio should delegate the partial class C to you using the technique in RFC
> 2317.
>
>