3 ms·
Who you using for DNS? iirc archive.today had a falling out with Cloudflare DNS because of a way they passed the requests onto archive.today so they stopped ans
by Crosseye_Jack 5y ago
Who you using for DNS? iirc archive.today had a falling out with Cloudflare DNS because of a way they passed the requests onto archive.today so they stopped answering requests from Cloudflare DNS.
EDIT: See https://news.ycombinator.com/item?id=28495204 https://news.ycombinator.com/item?id=28495204 for more info and https://community.cloudflare.com/t/archive-today-does-not-resolve-with-1-1-1-1-works-fine-on-other-resolvers/71315 https://community.cloudflare.com/t/archive-today-does-not-re... from a few years ago. They may of "made up" since, but I've not been using CF for DNS for a while now.
- denysvitali 5y agoOh yes, that's it. It seems like Google DNS is blocking it too for some reason: https://dnschecker.org/#A/archive.fo https://dnschecker.org/#A/archive.fo Weird. I have now switched to my provider's DNS to overcome the issue :)
- Crosseye_Jack 5y ago> Google DNS is blocking it too for some reason iirc, its not CF blocking the domain, its archive.today returning "bad" info when queries come from CF because disagree with the data CF give them. For me, (I just checked) I get a valid ip for archive.today when I dig via CF however the server it returns is hosted in Hong Kong but a query via my ISP's DNS servers returns a server in the Netherlands.