zlacker

[return to "Does Cloudflare’s 1.1.1.1 DNS Block Archive.is? (2019)"]
1. 7sovar+09[view] [source] 2023-08-02 14:19:30
>>lolind+(OP)
Hmm, no clue but if i ask 1.1.1.1 for the a record for archive.is i get 89.253.237.217

asking the office DNS the same question i get 51.38.69.52, asking 9.9.9.9 it gives me the same IP as the office DNS. Finaly asking google or 8.8.8.8 i also get 51.38.69.52

So i think their record is borked.

◧◩
2. bombca+S9[view] [source] 2023-08-02 14:23:29
>>7sovar+09
Supposedly Cloudflare uses a feature of DNS archive.* doesn't like, or vice versa.

Nobody cares; the reality is if you use CF DNS, shit don't work.

◧◩◪
3. jeroen+5b[view] [source] 2023-08-02 14:29:06
>>bombca+S9
It's not just Cloudflare, it's any DNS resolver that doesn't implement EDNS extensions. If you (or the company you work for) run a recursive resolver that doesn't submit such data, you'll run into the same issues.

I've switched to archive.org because archive.* is broken. For stuff that .org doesn't have, there's always the Tor version. The Tor address seems to be more responsive as well, so that's nice.

[go to top]