reverse dns problems

[Andris Kalnozols]

> Derek Balling <dredd at megacity.org> wrote:
> 
> I'd say the problem looks like they didn't do a 2317 delegation but 
> simply individually delegated all 128 addresses in 208.21.15.128/25 
> to ns1.mfin.com.

Correct.

> That's certainly NOT what I would expect to have happen in that
> circumstance.
> 
> I'd expect to see the cname-hack/2317 address be referenced by 
> ns1-auth.sprint, and pointing THAT subdomain at the ns1.mfin.com.
> 
> I'm not sure if what sprint has done would work (it might, come to 
> think of it), but its certainly not "expected by the rfc behavior".

What Sprint has done is force its customer to create 128 separate
zone files - one for each PTR, e.g.,

$TTL 1D
$ORIGIN 128.15.21.208.in-addr.arpa.
@      IN SOA    ns1.mfin.com. ed.alcpress.com. ( 1 3H 1H 1W 10M )
       IN NS     ns1.mfin.com.

       IN PTR    some.domain.name.

The RFC-2317 delegation method would have required the creation of
just one master zone data file.

Andris Kalnozols
Hewlett-Packard Laboratories
andris at hpl.hp.com