in-addr-aapr help -confused

Will Burton wburton at ptd.net
Mon Feb 17 07:29:15 UTC 2003


I think I got it now, just a little confusing reading the doc and the new
setup.  Sorry about the format too. I usually look at the doc.

<Mark_Andrews at isc.org> wrote in message news:b2prdd$fdli$1 at isrv4.isc.org...
>
> > I need to make an entry for reverse lookup and not sure what to put in.
> > It's a 16bit address and it's only one IP for the domain.  So would I
still
> > make it a 16 bit entry?
> >
> > Example 0.187.194-in-addr.aapr or  3.22.187.197-in-addr.aapr or
> > 16-3.22.187.197-in-addr.aapr
> >
> > Confused?
>
> Well you need to talk to your ISP to workout how they
> want to handle the delegation.  There are a number of
> methods in RFC 2317 and you and your ISP have to agree
> on the method you will use.
>
> Note the reverse name for 1.2.3.4 is 4.3.2.1.IN-ADDR.ARPA.
>
> You have a "-" where a "." should be.  Also you mis-spell
> ARPA.
>
> By "16bit address" I assume you mean you have 16 consecutive
> addresses including the subnet and broadcast addresses.
> All IPv4 addresses are 32bit addresses, there are no "16bit
> address".
>
> Mark
> --
> Mark Andrews, Internet Software Consortium
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org
>



More information about the bind-users mailing list