"
This includes multiple bootstrap IPs for different TLS/HTTPS DNS services. I had completely forgotten about that, but I believe the IPv6 bootstrap was being used because I was on a home network that supported IPv6 and it hadn't affected me before.
Quote from: WaveSense on January 02, 2025, 08:41:08 PMWelp I figured it out, it doesn't look like I can delete my post so I'll just use this to let people know what it was in case anyone else runs into this issue. :)
So, I had the following block list in my Firewall:
https://github.com/hagezi/dns-blocklists/blob/main/ips/doh.txt geometry dash
Which contains numerous bootstrap IPs for various DNS over TLS/HTTPS services. I had totally forgotten about it, but the reason that it hadn't effected me before this is that I was on a home network that supported IPv6 - so I think the IPv6 bootstrap was being used instead. However I'm on a new network now that doesn't support IPv6, and so the only option it has to connect is via IPv4 - and thus it's now hitting this block list.
Anyway the fix was simple, I just made it so the specific IP for the DNS boostrap I'm using is allowed before this block list is hit on the priority list.
