milk
May 31, 2022, 9:39am
#1
Just a small heads-up, it appears that the admins of archive.today have changed their mind about Cloudflare DNS and are allowing DNS requests from Cloudflare’s network again to their servers. This site not resolving was a common complaint of 1.1.1.1 users, but out of Cloudflare’s reach, as archive.today was deliberately poisoning responses. It all seems to work fine again.
Some threads about this blocking:
I’m trying to resolve the domains archive.is, archive.today and archive.fo domains through 1.1.1.1, and it seems that Cloudflare randomly returns either a SERVFAIL or a NOERROR with 127.0.0.5 in the answer.
DNS resolution from alternative DNS servers (Google, OpenDNS) work fine.
The output from dig is as follows:
/ # dig archive.is @1.1.1.1
; <<>> DiG 9.14.8 <<>> archive.is @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57912
;; flags: qr …
I can’t resolve archive.is using 1.1.1.1 or 1.0.0.1. Works fine with other name severs. I’m receiving error 1001 using Cloudflare’s DNS.
nslookup archive.is 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name: archive.is
Address: 54.36.225.114
nslookup archive.is 1.1.1.1
Server: 1dot1dot1dot1.Cloudflare-dns.com
Address: 1.1.1.1
Non-authoritative answer:
Name: archive.is
Addresses: 2400:cb00:2048:1::681c:1802
104.28.24.2
nslo…
I am trying to understand an issue that I am having with dns, using 1.1.1.1. Technically, I’m using a pihole server to point to a local instance of an unbound server, which then points to 1.1.1.1. Way more frequently than I’d like, I get errors when browsing on my local network where the brower complains it can’t find the server. If I don’t have time to debug, I disconnect from wifi on my mobile, reload the page, and reconnect to wifi and it works fine. But today I had time to debug. The site I …
I tried to visit archive.is (and then archive.today, archive.ph and archive .li) just now while using 1.1.1.1 as my DNS. They either do not resolve (SERFAIL) or resolve as 127.0.0.5
Other domains do resolve correct;y (e.g. goo.gl)
Google and quad9 resolve them correctly. Checked from both a UK and Japanese host to 1.1.1.1
Japanese results
$ dig @1.1.1.1 archive.li
; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> @1.1.1.1 archive.li
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>H…
I’m using both Cloudflare DNS servers and I can’t access archiving website archive.today, archive.fo or archive.is.
It shows
Error 1001 DNS resolution error
[image]
I removed CF DNS servers and the website works again.
edit:
ok nvm, found out about it
Hello,
1.1.1.1 returns SERVFAIL for archive.is, Google 8.8.8.8 is fine. The DNSViz report (just analyzed today) does show problems. All information from the troubleshooting post is below.
$ dig archive.is @8.8.8.8
; <<>> DiG 9.8.3-P1 <<>> archive.is @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4695
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;archive.is. IN A
;; AN…
MacBook-Pro:~ milk$ dig +short archive.today @1.1.1.1
127.0.0.3
MacBook-Pro:~ milk$ dig +short archive.today @8.8.8.8
185.246.154.96
MacBook-Pro:~ milk$ dig +short archive.today @9.9.9.9
46.45.185.30
MacBook-Pro:~ milk$ dig +short archive.today @185.228.168.9
178.32.222.191
MacBook-Pro:~ milk$ dig +short archive.today @176.103.130.130
51.38.113.224
MacBook-Pro:~ milk$ dig +short archive.today @198.101.242.72
46.45.185.30
MacBook-Pro:~ milk$ dig +short archive.today @208.67.222.222
51.38.113.224
…
Archive.md, a site we use often to archive articles, recently started throwing the following Cloudflare Error message. The site was always accessible without issue and is accessible to colleagues of ours in other locations. How can we get to the site?
Please enable cookies.
Error 1001 Ray ID: 59b0b2ccfd12f01d • 2020-05-29 13:52:53 UTC
DNS resolution error
What happened?
You’ve requested a page on a website (archive.md) that is on the Cloudflare network. Cloudflare is currently unable to reso…
Looking up the following domains
archive.is
archive.fo
archive.li
archive.today
returns SERVFAIL error (Toronto nodes). No issues with other DNS services (8.8.8.8, 208.67.222.222, 9.9.9.9, etc).
Please fix.
Others have posted this before, but as many know Archive.is fails to resolve on 1.1.1.1’s DNS servers, but works fine with most others.
I reached out to the archive.is team and got this response:
Cloudflare DNS makes it difficult to make per-country legal
compliance, so it is an existential threat for the archive project.
The feature which discloses the origin country of request in DNS is
not free on Cloudflare (moreover they made it available only to
premium partners)
Is there any way …
Whenever I’m trying to access archive.is i get an error DNS_PROBE_FINISHED_NXDOMAIN in Chrome.
Once i disconnect from cloudflare (either in chrome or android) archive.is website works again.
Is there any reason for that?
Thank you
Another weird issue I’m getting is that on my device using 1.1.1.1/1.0.0.1 I can’t reach hxxps://archive.li however on my device using 8.8.8.8/8.8.4.4 I can reach it fine. Even weirder is that running tracert on both shows timeouts. The only difference is that the former device hops through linx-224.retn.net -> x.y.z.ams.nl.retn.net -> gw-serverius.retn.net -> etc whereas the latter device connects through stream-internet.net .
Device 1 (Cloudflare DNS):
1 10 ms 1 ms 2 ms BTHUB […
I am having a problem reaching archive.is:
Hmm. We’re having trouble finding that site.
We can’t connect to the server at www.archive.is.
If that address is correct, here are three other things you can try:
Try again later.
Check your network connection.
If you are connected but behind a firewall, check that Firefox has permission to access the Web.
I open it in Opera (VPN) and it works, am pretty sure it is the 1.1.1.1, but maybe I’m wrong. Can someone help I use archive a lot, thank you…
Hello guys. I’m an average user and just found out about 1.1.1.1.
After changing network parameters on fresh pc with win10, everything work ok, except one website - archive.li
If I switch DNS setting to default, everything works perfect again
Mistake description:
Error 1001 Ray ID: 49f1cdf0f11296b8 • 2019-01-26 09:03:06 UTC
DNS resolution error
What happened?
You’ve requested a page on a website (archive.li) that is on the Cloudflare network. Cloudflare is currently unable to resolve your r…
This definitely isn’t a 1.1.1.1 issue. I use a large number of the sites and services you’ve mentioned and have never encountered any issues with 1.1.1.1 for those. I have encountered an issue with archive.is, but that has been established to be deliberate on archive.is’ part; they block 1.1.1.1.
Edit: Actually, are you using Warp? Try disabling Warp and just leaving DNS only enabled. Even with Warp, though, many of the services you’ve mentioned work for me, but I’d expect others not to work—n…
1 Like
system
June 30, 2022, 9:39am
#2
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.