If you use Cloudflare's DNS (1.1.1.1), then the popular web archive archive.today (and the related sites archive.ph, archive.is, archive.li, archive.vn, archive.md, and archive.fo) will either fail to resolve, or show an infinite CAPTCHA loop. If it does resolve when you're on Cloudflare's DNS, you may have the domain locally cached.
Fix this problem by:
- Configuring
dnsmasqon your local DNS server to use an alternate DNS server for archive.today (see comment from @joshenders below), or - Connecting to a VPN before connecting to archive.today (only works if the VPN uses different DNS servers), or
- Temporarily switch DNS to resolve and locally cache the domain, then switch back to Cloudflare
This has been an issue since at least 2019. To check if this is still an issue today:
In PowerShell:
# Resolve archive.today using Cloudflare DNS
PS> Resolve-DnsName archive.today -Server 1.1.1.1 -DnsOnly
Name Type TTL Section IPAddress
---- ---- --- ------- ---------
archive.today AAAA 85976 Answer 2606:4700::1114
archive.today A 86400 Answer 1.1.1.4
# Resolve archive.today using Google DNS
PS> Resolve-DnsName archive.today -Server 8.8.8.8 -DnsOnly
Name Type TTL Section IPAddress
---- ---- --- ------- ---------
archive.today A 300 Answer 23.137.249.79In bash:
# Resolve archive.today using Cloudflare DNS
$ dig +short @1.1.1.1 archive.today
1.1.1.4
# Resolve archive.today using Google DNS
$ dig +short @8.8.8.8 archive.today
23.137.249.79If the A record resolves to 1.1.1.4 like in the examples above, then it's still an issue.
According to some reports online, this problem was resolved in May 2022. However, it looks like this resolution was only temporary because the sites will not resolve again as of July 2023.
As of August 2024 it looks like this issue is resolved. Meaning Cloudflare's DNS successfully resolves to the archive.today domains and there's no more infinite CAPTCHA loop. Hooray!
https://news.ycombinator.com/item?id=19828702
Problems with archive and NextDNS. Solved bij giving in manual entries to all adresses.