I do assign static IPv6 addresses on my pi, using the above described method (/etc/dhcpcd.exit-hook)
I use this to identify the different resolvers pihole-FTL is forwarding DNS requests to.
My hosts file contains these entries:
# dnscrypt-proxy v2
127.10.10.4 dnscrypt-IPv4
fdaa:bbcc:ddee:2::5554 dnscrypt-IPv6
# unbound
127.10.10.2 unbound-IPv4
fdaa:bbcc:ddee:2::5552 unbound-IPv6
the IPv4 addresses simply work, you don't have to do anything to use them in the configuration files of unbound and dnscrypt-proxy. The IPv6 addresses are assigned, using the above method (/etc/dhcpcd.exit-hook).
In my setup, these adresses are only useful on the pi, allowing pihole-FTL to forward to unbound and dnscrypt-proxy
Why? for this result in the dashboard:
I agree you should not assign GUA addresses, in any way (static or DHCPv6), this should be handled by auto-configuration, my pfsense assigns GUA addresses (track interface) to devices, derived from the IPv6 address my provider assigns to my routers WAN interface
You (DL6ER) once said "without IPv6, you're missing out on a big part of the internet". That is what triggered me to research and setup IPv6 on my network.
You also said on this forum, communicating over IPv6 is faster (more efficient) than IPv4, I hope you still support this statement.
So disabling IPv6? NO. Research the problem and try to fix it...