3 ms·
Just put the fixed IP addresses for the various archive.?? domains in your hosts file. This completely resolved the problem for me.
by lazyeye 3y ago
Just put the fixed IP addresses for the various archive.?? domains in your hosts file.
This completely resolved the problem for me.
- greenyoda 3y agoEven easier: Switch your browser's DNS-over-HTTPS configuration to another DNS provider. NextDNS works OK for me.
- lazyeye 3y agoGreat suggestion. Have just done this now too. For Windows users, YogaDNS is a great little app for managing DNS configuration. Can set up DNS rules depending on domain name etc. I actually use PiHole and added Local DNS entries for the archive.* domains in my PiHole config to fix the issue across my local network.
- noloblo 3y agocan you paste the relevant /etc/hosts lines
- codetrotter 3y agoIP addresses might vary depending on geo location or time. Here is what I get from DNS currently, that you can put in your /etc/hosts 51.38.69.52 archive.is archive.today 41.77.143.21 archive.ph archive.li archive.vn archive.fo archive.md And if all else fails, install Tor and access their site at archiveiya74codqgiixo33q62qlrqtkgmcitqx5u2oeqnmn5bpcbiyd.onion