Hi, well I use Kea for ipv6 and v4. For ipv4 I have a bunch of reservations with hostnames that get tracked in Unbound. I also have some infrastructure that is in the same subnet but outside the DHCP pool for ipv4. I use unbound overrides for those to get dns resolution.
For ipv6, kea provides the dhcp and the standard router advertisement daemon in services is in assisted mode. This enables the LAN clients to get an ip from the ISP assigned /48 prefix (LAN interface configured as tracking WAN. WAN configured as DHCPv6). I use two subnets inside the ISP assigned prefix length to provide two VLANs with separate ipv6.
As for local client IPv6 tracking and reservations as well as DNS, do not use that. Internally the clients get a IPv6 from the earlier mentioned infrastructure and that is routeable through the ISP ipv6 gateway. Internal local LAN traffic is all done with IPv4, DNS ipv4 and a Caddy reverse proxy (https with SSL wildcard certs) where applicable.
For all configurations I used guides from either this forum and/or documentation.
For ipv6, kea provides the dhcp and the standard router advertisement daemon in services is in assisted mode. This enables the LAN clients to get an ip from the ISP assigned /48 prefix (LAN interface configured as tracking WAN. WAN configured as DHCPv6). I use two subnets inside the ISP assigned prefix length to provide two VLANs with separate ipv6.
As for local client IPv6 tracking and reservations as well as DNS, do not use that. Internally the clients get a IPv6 from the earlier mentioned infrastructure and that is routeable through the ISP ipv6 gateway. Internal local LAN traffic is all done with IPv4, DNS ipv4 and a Caddy reverse proxy (https with SSL wildcard certs) where applicable.
For all configurations I used guides from either this forum and/or documentation.