I have a /64 from HE via tserv9.chi1.ipv6.he.net (184.105.253.14) and from my dual stack LAN hosts behind pfsense via Stateless DHCP (not DHCPv6), I recently be

I have a /64 from HE via tserv9.chi1.ipv6.he.net (184.105.253.14) and from my dual stack LAN hosts behind pfsense via Stateless DHCP (not DHCPv6), I recently began having trouble searching via Google's search engine over IPv6. Including via Chrome browser's search bar and Firefox the same, also just a straight up search from site google.com and to verify, the same from ipv6.google.com. I get great speeds via Xfinity speed test (IPv6 & IPv4) over Spectrum Business Class rated at 300Mbps. I considered getting a /48 as recommended, but I wondered if plain old firewall rules for LAN might help. Rejecting all LAN IPv6 to an alias containing every Google search hostname and IPv6 address I could find. And it actually worked. Only the Google Search IPv6 addresses are blocked up high in the rules so Google falls back to the IPv4 search addresses, which I don't have to declare, it just falls back from IPv6 to IPv4 Google search pages and the multi-bar. Of course DDGo is always a preferable option for searching, but on Android devices Google Search is so integrated it's easier to live with Google. Such a simple solution and it works, so I'm not arguing. Every other Google app continues to run over IPv6 including Gmail,Drive, Docs, Youtube, etc. I am blocking IPv6 per: google.com, www.google.com, ipv6.google.com, 2607:f8b0:4023:1004::64, 2607:f8b0:4023:1004::65, 2607:f8b0:4023:1004::71, 2607:f8b0:4023:1004::8b, 2607:f8b0:4006:81f::200e, 2001:4860:4860::8888, 2001:4860:4860::8844