Cloudflare blames Archive.is and Archive.is blames Cloudflare.
However I do think this has something to do with 1.1.1.1 not supporting eDNS. People have reported issues with accessing bbc.co.uk over it too.
This is unfortunately something we can’t do something about.
Nameservers responsible for archive.is (ben.archive.is,
anna.archive.is) are returning answers tailored to the IP address of
the requestor. They return the 54.36.225.114 when asked from my
residential address:
54.36.225.114
But wrong address when queried from Cloudflare’s network:
104.28.24.2
If you have a contact on the domain owner, you can ask them to fix
this.
I’m not sure if we read the same article - the VPN is a full VPN. Their servers only cache non-ssl traffic. All traffic to/from your device is still going through their servers.
I just let DNScrypt-proxy chose the fastest one from a large list of trustworthy servers automatically and exclude any that log, censor or don’t support DNSSEC.
Their article states that about half as much DNS traffic goes through them as goes through Google.
That is not an argument, The amount of Data that flows through Google is alarming as well, but just moving from one large Central provider to another is not a solution to that problem
I trust neither Clouldfare or Google, both have done things that should question their ability to be independent operators of core infrastructure
Unless youre maintaining your own DNS you have to trust someone eventually. I trust Google less and my ISP less, and other than Cloud flare who else is there that has decent speed?
Even if you are maintaining your own you still have to trust someone, that is how recursive DNS works. however I do run my own servers, and use a variety of sources such as Quad9, OpenDNS, DNS Watch, Level3, and my ISP (I do trust them more than google)
Further depending on your ISP i would most likely trust them more than Google, there is not many companies I trust less than Google