Website Momentary Connection Reset Errors DNS IPV6 Lookup Failure err_connection_reset

Starting a couple of months ago my machine started having issues loading websites where sporadically I'd get err_connection_reset briefly then the website would load a second later.  I've done SysAdmin in the old days so I knew the logical steps to rule things out.

1. Browser ruled out, it did it in Edge, Chrome, and Firefox

2. Browser cache issue rules out - did it after clearing cache. In fact, I could somewhat reproduce the problem more consistently if I cleared the cache then tried to load a site like Amazon.

3. Ruled out specific website, did it on multiple sites including the like of Amazon.com.

4. Ruled the Windows firewall and anti-virus. Disabled them. Still happened.

5. Ruled out Internet connection, pings to different servers looked good. Logged into the router and no excessive packet errors.  Restarted WIFI router of course.

So I hadn't opened up a command prompt in a long time and did a manual DNS lookup (nslookup). Tried it recently and couldn't look anything up as the nslookup command was trying to lookup by connecting to the DNS server using its IPV6 address! I know DNS is set via DHCP via my ISP (AT&T Fiber Home Internet). I also know by default IPV6 is enabled on Windows 11.

Disabled IPV6 and the nslookup worked fine going back to IPV4.

This seems to logically explain the issue as probably the connection reset error was due to a brief DNS lookup failure then it would load a second later after probably trying IPV4 DNS lookup and this lookup would be cached. So when I cleared the cache the problem would happen again.

It looks to me as AT&T changed their DNS server setting for DHCP and is pointing to an IPV6 address that is not responsive! Or it's a Windows 11 specific issue after some update?

I may be Windows 11 related as if I recall I also tried tethering my phone and still had the issue BUT, I'm using a reseller of guess which cell service? AT&T. LOL.  Not sure if the DNS servers are the same.

This is the response I get when I have IPV6 turned on:

nslookup yahoo.com
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  2600:1700:79b6:f410::1

The IPV6 address is of course an AT&T device.

Here is with it off forcing IPV4

nslookup yahoo.com
Server:  dsldevice.attlocal.net
Address:  192.168.1.254

Non-authoritative answer:
Name:    yahoo.com
Addresses:  2001:4998:124:1507::f001
          2001:4998:124:1507::f000
          2001:4998:24:120d::1:1
          2001:4998:44:3507::8001
          2001:4998:24:120d::1:0
          2001:4998:44:3507::8000
          74.6.143.25
          98.137.11.163
          98.137.11.164
          74.6.231.20
          74.6.231.21
          74.6.143.26

I could manually set the DNS addresses for IPV6 to Google's servers but this could eventually be an issue if ever you connected to a WIFI that required login (airplane, restaurant) to the network.  It gets the address for the site to log into from the DNS server the wifi router is set to.  Virtually all wifi networks are going to support IPV4 fallback I would imagine if they ever got to preferring IPV6.