HELP
Bob Vance
bobvance at alumni.caltech.edu
Tue Feb 6 02:07:30 UTC 2001
Yikes !!!!
I really should get out more!
and read the RFCs ~%-/
Thanks. At least I have the solace of having figured it out on my
lonesome :|
-------------------------------------------------
Tks | <mailto:BVance at sbm.com>
BV | <mailto:BobVance at alumni.caltech.edu>
Sr. Technical Consultant, SBM, A Gates/Arrow Co.
Vox 770-623-3430 11455 Lakefield Dr.
Fax 770-623-3429 Duluth, GA 30097-1511
=================================================
-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Mathias Körber
Sent: Monday, February 05, 2001 8:30 PM
To: bobvance at alumni.caltech.edu; bind-users at isc.org
Subject: RE: HELP
Yes, this works and some people are doing it this way.
See RFC2317 section 5.2 :-)
> A simpler classless solution -- no delegations and NS records, no new
> zones or anything.
>
> In the parent, "normal" reverse zone do this :
>
> ;;;$ORIGIN 199.22.195.in-addr.arpa.
> @ IN SOA ...
>
> ... ;;; your stuff
>
> ;;; remove their current PTRs.
> ;;; then add:
> $GENERATE 64-95 $ CNAME $.cl-rev.somedomain.com.al.
>
>
> Here, you have set up the "real" reverse-lookup data as aliases
pointing
> to their zone. Note that there is no additional delegation here.
More information about the bind-users
mailing list