PTR records for v6 hosts

[Martin Millnert]

On Mon, 2009-08-31 at 11:41 +0200, Bjørn Mork wrote:
> Ron Broersma <ron at spawar.navy.mil> writes:
> 
<snip>
> 
> Nice solution for dual stack hosts.  But how do you plan to support IPv6
> only hosts?
> 
> And does anyone have a proposal that would fit an ISP environment? Lets
> say you use DHCP-PD to delegate a prefix to a customer, who is in full
> control of his own "residential gateway" so you can't look up his
> neigbour table.  What do you do?
> 
> - Delegate the reverse zone to the customer?  Most won't have a clue
>   what to do with it.
> - Provide a DDNS solution for the customer and not care whether they use
>   it or not?  Most won't use it.
> - Set up an IPv6 "walldns" (to borrow terminology from DJB)?  I don't
>   really see the point.  How is a pointer record like
>   x20010db800000000021a73fffe502834.example.com better than just not
>   having a pointer?
> 

Hi,

as long as you delegate a coherent prefix (and remember which one), you
can always at the bare minimum set up a wildcard match for your branch
of the ip6.arpa tree, that points to some customer name. BIND supports
this at least. You probably have to understand how labels and wildcard
matching works (see RFCs) to understand how to use it though. (I think
most people on this list do though :) )
  For forward records I believe the easiest thing to do is to let users
manage that themselves via some web application, if you have the support
for that.  We (ISP) are going to implement this soon.

And generally, I think they primary key everbody is looking for (but not
everybody can utilize, of course), is an interface's MAC address
(optionally tied to interface's owners - the host's - hostname, if you
want), not the interface's IPv4 domain name.  We are lucky enough to be
able to use L2 information ourselves, so, we're going for the MAC as a
key.  To make things better, we're just going to setup classic default
names for the addresses, but let users have the possibility to override
these names with their own names.
  Updates go via a web interface, and not DDNS. Really don't see how
anything get's better if typical stupid user's windows-hostnames, that
usually make no sense whatsoever, go into the domain name system.

Cheers,
-- 
Martin Millnert <martin at millnert.se>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20090831/cce70bd9/attachment.bin