PTR records for v6 hosts

[Mark Milhollan]

On Mon, 31 Aug 2009, Lionel Elie Mamane wrote:

>>- Delegate the reverse zone to the customer?  Most won't have a clue
>>  what to do with it.
>
>I can imagine that once IPv6 support has "settled in", that will be
>the standard solution, supported by most residential gateways.

Most of todays "settled in" consumer IPv4 gateways don't know their own name 
in any meaninful global DNS terms.  Internally most are unnamed, but I've 
seen several that disclose the PPPoE username or are plain router or 
$routermodel or similarly useless things.  Hell, many "managed" routers for 
non-trivial clients don't have a useful hostname set.

Perhaps the manufacturers will provide something, but don't expect anything 
better than the semi-horrible walldns-like example already suggested 
(x20010db800000000021a73fffe502834.example.com), for privacy if not 
performance reasons, i.e., some (probably many) people would be freaked if 
you suggested that their router publish in some form the (idiotic or too 
revealing?) hostnames they have themselves assigned (often unknowingly).

Also some ISPs would want to force the domain, but where is the domain name 
delegation to complement the address prefix delegation?  Without that the 
gateway couldn't properly respond (Mark-PC.local anyone?), for this case, 
which means filtering the response (so no longer a direct delegation, and 
thus more complex systems).

I expect an ISP provided, predefined generic name for every address in the 
entire allocation will predominate for many years, making things like Martin 
List-Petersen's pdns pipe very attractive (since it would kill BIND, and 
others, to actually populate such a zone).  Perhaps using base 32 (or 64) 
encoding instead of merely 16, easy as it is to "see" the ip address when 
using hex.