Museum decides a Roman Emperor was transgendered.
(archive.ph)
You're viewing a single comment thread. View all comments, or full comment thread.
Comments (32)
sorted by:
LIke others said, it's a DNS issue. The guy who runs the archive.today network is kind of a dick and deliberately configures his stuff to confound browers and DNS servers he feels you shouldn't be using. So some resolvers just plain don't work.
I use pihole so my workaround is to manually configure dnsmasq to hit up a DNS server I know works for those sites. I don't use it all the time because it's kind of slow from my ISP for some weird reason.
"Just use OpenDNS" isn't good advice considering their practically butt buddies with the WEF.
Yes, all public DNS server are compromised in some way, but, in general terms, I'd recommend poking around a bit and picking one with the fewest downsides for your priorities.
I don't think it's DNS for me. The report I get is a closed connection. It doesn't matter if I set it to use public DNS (like 1.1.1.1) or ISP or force secure DNS. Those servers don't seem to care. I used to have to use a different VPN.
Of course, I used to be blocked. Lately, I've had no trouble with the network. And I didn't change DNS (currently still secure DNS via ISP).
DNS isn't really secure, but neither would I rely on it being? Pretty much every site uses https with a certificate these days, and I'm not sending them any data if they don't (view-only content is fine). So I don't really care what your IP address is. If you have the private key then I suppose you are the one responsible for that website. That could also go wrong, but you try.