Hmm, so that is what Windows does, seems strange (Like, the DNS server shouldn't allow any random system to update records, it should only allow a trusted client)
Won't work in a mixed setup though, where you have Linux and Windows clients, or use a non Windows Server DNS server (like bind)
Edit: And putting the logic in the DHCP server allows for stuff like batching, restoring DNS info across restarts, etc.
I just checked and it is only Windows clients that do this through dynamic registration (or whatever it is called). It looks a lot easier to manage with DHCPv6. I suppose just using stateless is good for a 'click and go' situation.
I have a question though. What happens with DHCPv6 clients and the Temporary IPv6 address? Does that also show up in the management console as a EUI64 (i.e. does it register somewhere aswell)? Usually the temporary address is the preferred source for IPv6 data from a host. I am unable to try this out for myself.
It would be hard to keep track of some things in a mixed environment with all these different addresses and the temporary ones too.
Time for bed.