IPv6 and DNS for the residential service provider

[Ted Mittelstaedt]

They only NEED rdns if they are running a mailserver or some other 
server on IPv6 that is going to have a fixed IP in which case you
can manually create those records.  Yes I know people would like to
have rdns for residential customers but how is the Internet served
by having ten million resolvable rdns names on the variation of 
DELL1235465SERVICETAG395482323.workgroup.mshome or some such rubbish?

Ted

On 9/24/2012 11:32 AM, Ron Vachiyer wrote:
> Hello, (hopefully on-topic for this list!)
>
> I am looking for some tips as to how to deal with DNS and rDNS in a
> residential service provider scenario.  This document,
> http://tools.ietf.org/html/draft-howard-isp-ip6rdns-02, doesn't seem to
> have been updated in ages and I haven't found any more recent pertinent
> information.
>
> Basically, this doc offers the following options to provide forward and
> reverse DNS; our customers are residential and will not be asking for,
> or in a position to, operate reverse delegations themselves.
>
> 1) not answer at all (NXDOMAIN).  This breaks applications that check
> forward>reverse
>
> 2) wildcard reverse DNS.  This also breaks forward>reverse since as far
> as I know you can't have a wildcard forward lookup?
>
> 3) Dynamic DNS updates.  At first this sounds interesting, except that
> from what I can tell most current OSs don't by default register in DNS,
> and if they do, don't use the domain obtained by DHCP unless that is
> enabled as well.  And, IP-based DNS updates are inherently insecure.
>
> 4) delegate DNS to the customer gateway (never heard of a platform that
> actually supports this??)
>
> 5) "on the fly" record creation.  I find no doc for this other than a
> vague PowerDNS reference, does BIND support something like this?
>
> Any tips appreciated, RTFM links, whever.
>
> Thanks,
>
> Ron