4 ms·

Does not work for me, plus SSL error :|

• Operyl 6y ago
  You're using 1.1.1.1 for your DNS resolver. Archive.is has this hatred with them, and purposely serves a bad record to Cloudflare's resolver as a "retaliation." The SSL error you're seeing is because they (that is, archive.is authoritative server) returns the IP 1.1.1.1 when 1.1.1.1 is used to resolve the A record. I should reiterate: this is archive.is' doing this, not Cloudflare. EDIT: Some more details, including quotes from Cloudflare's CEO from another internet citizen: https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ EDIT2: I should mention that I still use 1.1.1.1, and I agree with their stance on this. :)
  • adamhearn 6y ago
    This is really bad. I don’t love cloudflare, but I do use their dns. This makes me want to support them with my business and makes me wish I could take back my archive donations...
  • imjustsaying 6y ago
    Judging by the tweet, the archive.is admin says the lack of the EDNS data causes many problems. Maybe it increases his operating costs too? Archive.is a free service and goes offline frequently so I'm inclined to believe he's really trying to triage the problem queue, unless I'm missing something.
    • Operyl 6y ago
      Plenty of other providers/projects are able to geo/load-balance based on many other factors, like request IP. I dunno, I just feel like it's a dumb hill to die on.