IPv6 and DNS for the residential service provider

[Bjørn Mork]

Ron Vachiyer <proutfoo at outlook.com> writes:

> 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

really?  Like what?

> 2) wildcard reverse DNS.  This also breaks forward>reverse since as
> far as I know you can't have a wildcard forward lookup?

yup, broken

> 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.

can be solved.  But is there a point?  I.e. a big enough gain making it
worth the cost/effort?

> 4) delegate DNS to the customer gateway (never heard of a platform
> that actually supports this??)

That can be implemented, given enough demand.  But it basically boils
down to the same question as above.

> 5) "on the fly" record creation.  I find no doc for this other than a
> vague PowerDNS reference, does BIND support something like this?

well, you could run something based on e.g
http://member.wide.ad.jp/~fujiwara/v6rev.html

But personally I think you can just as well ignore reverse DNS for 
residential customers.  I'd like to enable delegation and/or dynamic
updates for those who want it, but I don't think it is a mass market
product. 


Bjørn