Short answer: no. Quite the opposite, actually — Archive.is is intentionally blocking 1.1.1.1 users. Here's why.

tl;dr: No. Quite the opposite, actually — Archive.is’s owner is intentionally blocking 1.1.1.1 users.

CloudFlare’s CEO had this to say on HackerNews:

We don’t block archive.is or any other domain via 1.1.1.1. […] Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service. […] The archive.is owner has explained that he returns bad results to us because we don’t pass along the EDNS subnet information. This information leaks information about a requester’s IP and, in turn, sacrifices the privacy of users.

I am mainly making this post so that admins/moderators at BeeHaw will consider using archive.org or ghostarchive.org links instead of archive.today links.

Because anyone using CloudFlare’s DNS for privacy is being denied access to archive.today links.

https://ghostarchive.org/archive/PmSkp

  • feyo
    8·
    1 year ago

    Quad9, DNS.Watch, OpenDNS

    Three good alternatives.

    • normal_user@lemmy.one
      6·
      1 year ago

      Also NextDNS is great because you can change every setting (and the free tier offers you way more usage than you will ever use)

      • notfromhere@lemmy.one
        3·
        1 year ago

        I maxed out the free tier in my first month somehow lol… $20/yr isn’t a bad deal for essentially pihole everywhere.