Delegation of CIDR Block
Bob Vance
bobvance at alumni.caltech.edu
Tue Feb 13 15:58:12 UTC 2001
>This only works if they are all part of rev.cust.com.
That's really a non-sequitur.
They *are* part of " rev.cust.com." because that's where you told the
ISP to point the $GENERATE CNAMEs to and that's where you put the
PTRs :)
It doesn't matter what domain the PTRs are in. All that matters is
what *they* *point* to:
ISP:
$ORIGIN 33.172.209.in-addr.arpa. ;;; or whatever
...
$GENERATE 16-31 $ CNAME $.rev.cust.com.
Customer:
$ORIGIN .cust.com.
...
17.rev IN PTR foo.sub-dom1.cust.com.
18.rev IN PTR bar.sub-dom1.cust.com.
19.rev IN PTR foo.sub-dom2.cust.com.
20.rev IN PTR bar.sub-dom2.cust.com.
21.rev IN PTR foo.cust-dom2.com.
22.rev IN PTR foo.cust-dom3.com.
23.rev IN PTR foo.cust.com.
foo IN A 209.172.33.23
yada yada
Note that there are no "A" records in this case, except for those
guys that are actually in "cust.com." .
The "A" RRs for the others are in their respective forward zones.
-------------------------------------------------
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 Charles Bodley
Sent: Tuesday, February 13, 2001 9:52 AM
To: bobvance at alumni.caltech.edu; bind-users at isc.org
Subject: RE: Delegation of CIDR Block
This only works if they are all part of rev.cust.com. Is there anyway to
do
it reguardless of the domain it's under? A friend has the same problem.
He
wrote the code and is hosting 20 different domains. He only bought 32
IP's.
Is their any similer move for multiple domains?
-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Bob Vance
Sent: Tuesday, February 13, 2001 9:17 AM
To: bind-users at isc.org
Subject: RE: Delegation of CIDR Block
Thanks.
>it is often less work to make changes that customers need on a demand
>basis, than battling ongoing problems caused by customers running the
>masters badly.
That's the type of info I wanted :)
I really hadn't thought of that (since *I* never made an error when I
ran the DNS :).
Of course, in this case the ISP is *already* letting him master the
forward domain, but just doesn't want to let him do a partial reverse.
A single line in the ISP reverse domain would do the trick:
$GENERATE 16-31 $ CNAME $.rev.cust.com.
Then the customer can put the PTRs right in the forward zone:
$ORIGIN .cust.com.
...
foo IN A 1.2.3.4
19.rev IN PTR foo
So what's special about the reverse data that the customer might screw
up as opposed to the forward data he already has control of?
Hmmm. Maybe breaking a reverse and then complaining that he can't send
mail to some site whose mail system wants to do a reverse lookup :)
-------------------------------------------------
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
=================================================
More information about the bind-users
mailing list