Delegation of CIDR Block

[Bob Vance]

>> A single line in the ISP reverse domain would do the trick:
>>
>> $GENERATE 16-31 $  CNAME  $.rev.cust.com.
>
>Is that all the isp has to do?

Well, he has to bump the serial number and reload the zone, of course.

Then the changes have to propagate out to the rest of the name servers
authoritative for that reverse zone.

And cached entries in the rest of the world have to time out :)


>How can I convince an isp that my dns config is ok?

Haven't got an answer for that one.
Someone else ?


-------------------------------------------------
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: Philipp Snizek [mailto:mailinglists at belfin.ch]
Sent: Tuesday, February 13, 2001 10:20 AM
To: bobvance at alumni.caltech.edu
Subject: AW: Delegation of CIDR Block


> A single line in the ISP reverse domain would do the trick:
>
> $GENERATE 16-31 $  CNAME  $.rev.cust.com.
>

Bob,

Is that all the isp has to do?
How can I convince an isp that my dns config is ok?

Thanx
Philipp


> 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 :)
>
>