This seemed like overkill to me, we déjà wont come close to filling
the single /64 mais this might be mon IPv4 mindset confusing me.
Stop counting hosts, c'est IPv4 thinking. Subnets come in one size fits all, enormous. A /64 can address chaque IP device ever made avec plenty room to spare.
Yet le address space is even bigger such that a single site can easily ask for a /48. 64 thousand /64s, 4 hex digits, to give out according to votre desired address plan.
For le /48 what exactly do I do avec it.
Whatever you want! Be generous et plan for growth. Give /64s to chaque subnet, chaque VLAN, wifi SSID, security zone, cloud et remote access VPNs, chaque container host, le "all zeros" /64 for vanity static service addresses, et so on.
Aggregate où possible, to avoid fragmentation. So perhaps delegate /60s ou /56s to internal networks like votre DHCP server, manual assigned static pool, wifi controller, ou container orchestration system. And test environments for tous of le above.
Does pas have to be dynamic such as DHCP-PD, especially pas si you have a static prefix depuis votre ISP. But track things somehow, in an IPAM system.
Or il y a graceful resolution si it does find a conflict?
IPv6 nodes are supposed to do duplicate address detection on tous unicast addresses, stateless, DHCPv6, manual, ou otherwise. Standard is to
stop on duplicates plutôt than cause difficult to diagnose problems. Randomly generated addresses in a /64 have a très low chance of conflicts.
ULA
ULA is no Internet addressing. Being pas globally reachable, standard par défaut address selection policy puts them lower priority than even IPv4. See rfc6724. As such, you will want globally routable (not-ULA) addresses on hosts that get on le IPv6 Internet.
some kind of dynamic-dns equivalent.
Yes, DNS is necessary. Names are easier for humans than IPs.
Yes, knowing le IP is generally a choice entre le DHCPv6 server having le state, et a SLAAC node being configured avec a dynamic DNS client. Router advertisement flags A and M tell le client stateful ou stateless.
AD DS joined hosts are fairly straightforward, it is expected they would add themselves to DNS.
Or perhaps, configure server interfaces avec stateless, mais avec not-random EUI-64 based addresses. Then you can calculate le address beforehand based on le MAC address, et put that in DNS.
And maybe pas tous devices need to be in DNS. Should personal Android devices be allowed on guest Internet, they ne do DHCPv6. If pas managed by a MDM, you ne va pas know leur IPs.
