You cannot set the Windows DHCP/DHCPv6 server to listen on dynamic addresses or all addresses, only static addresses. Is there a technical reason for this limitation? Is there any workaround?
My specific situation:
I am using Router Advertisements to configure IPv6 hosts in this network. The address prefix is acquired from upstream routers and MAY change without notice. The Windows DHCPv6 server in question is only configured to distribute domain search lists and other non-address related configuration (it configured for stateless mode and does NOT configure addresses).
The DHCPv6 server could configure it's own address using the same Router Advertisements but then will not respond to requests. I cannot configure it to use a static address because it will break once the prefix changes.
I do realize I can set up a ULA in this subnet but that is a last resort (not an answer).
UPDATE: There has been some question is whether dynamic IPv6 routing is a good idea. I consider it a necessity even if your ISP provides static prefixes. It must be used in order to be able to quickly re-route from fail-overs and to imitate other functionality provided by pseudo-routing in IPv4 NAT.
Best Answer
Now I know I said setting up a ULA was not an option but it is actually far easier than I thought. You do not need to publish the prefix. And no other address in the ULA subnet even needs to exist anywhere.
Yes, it is a garbage address that clutters up the routing table but at least it doesn't get into other machines.
Hopefully Microsoft will take note at some point and allows their DHCPv6 server to respond on other available addresses besides static. It makes sense to require a static address during stateful address assignment in order to reliably map scopes to interfaces. But it does not apply to stateless DHCPv6.
Unfortunately, there is no other answer to this question.