Interesting thoughts.

You are correct that Cisco has not (to my knowledge) implemented the features described in RFC 6106. I suspect it will be very soon, though. Also, it’s not just the routers that are not sending it. The clients may not be ready to receive it either. I have not tested it but I hear that Windows7 currently needs an add-on (3rd party). It is here: http://sourceforge.net/projects/rdnssd-win32/. I have also read that Ubuntu 11.04 (as a client) natively supports RFC 6106. Other ‘nix distros may need some help for the time being (but not for long, I’m sure).

I am unaware of anything that would save the clients from the responsibility of registering themselves with DNS when stateless autoconfiguration is being used. There is no interaction with DHCP in the process of getting an address. Cisco’s nd other-config-flag will send clients to DHCP for DNS and domain suffix info but they are still getting their addresses through their in-house mechanisms (random or MAC-based).

If you want to preserve your DHCP server’s ability to register the addresses with DNS you are heading down the road to a stateful DHCP environment.

Colin

Now one thing still remains, in my opinion. I have been using on Linux ISC DHCP server for DHCPv6 together with Bind 9.7, and this combination allows DHCP to perform dynamic updates of Bind zones with the names and IPv6 addresses of DHCPv6 clients.

But if I move to using RFC6106 completely, then the burden of dynamic DNS updates falls on the IPv6 clients, or am I wrong?

Basically, I want to ensure that all my IPv6 clients still get an AAAA record on my DNS server, regardless of how the clients get their IPv6 address and DNS server information.