"Long time listener first time caller!" - Thank you in advanced for any help! I'll try to be as brief and technical to prevent indigestion.
I'm having an issue with my Server 2019 DC (Hyper-V)M on non-joined host not Forwarding IPv6. It DNS and Forwards IPv4 without any issues even SSL. It DNS IPv6 all the way to the internet, but it's not seeming to forward packets past DNS. Any IPv6 ping/tracert request past the Gateway host (from the DC host) time out. Any IPv6 ping/tracert request past the DC host (from a client) time out. IPv4 makes it all the way there and back again.. My Edge Gateway is a pfSense VM router on a separate physical Hyper-V host. From that Gateway I can ping/tracrt IPv6 to the internet without an issue. I am purposely routing the Domain through the DC.
Topology:
- Server 2019 DC/DNS/DHCP
- RRAS(LAN Router) - Routing both IPv4 & IPv6 options Lan Routing
- DHCP serving both IPv4 & IPv6, IPv6 server option 0023 set to DC address
- NICs: LAN & WAN two physically separate/virtual switches
- Local Domain to LAN -> RRAS (LAN Router) -> WAN to Gateway LAN -> Gateway LAN through Firewall through Gateway WAN -> Internet
- Gateway/Firewall/Cache/RA: pfSense (Hyper-V)M forwarding to a remote Gateway
- NICs: LAN & WAN two physically separate/virtual switches
Here are some screenshots of the configuration for the adapters and tracing the route:




tracert from DC:
tracert from a client: