![](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="48" height="48"><rect fill-opacity="0"/></svg>)
![](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="680" height="340"><rect fill-opacity="0"/></svg>)
1
3
14
ツイート
会話
![](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="600" height="265"><rect fill-opacity="0"/></svg>)
yes, unlike other public DNS services, 1.1.1.1 does not support EDNS Client Subnet
1
10
I mean aren't you all customers, are there any plans to get this resolved? I'm sure there are 100k+ users who can't access the site and don't know why
13
このツイートは、ツイートの作成者により削除されました。詳細はこちら
"Having to do" is not so direct here.
Absence of EDNS and massive mismatch (not only on AS/Country, but even on the continent level) of where DNS and related HTTP requests come from causes so many troubles so I consider EDNS-less requests from Cloudflare as invalid.
It's ECS specifically that wants. ECS is a protocol for passing along the IP address of the querying client to the authoritative nameservers. It's a privacy issue, which is why deliberately omits it.
1
11
返信を表示
Am I going to have to manually set my DNS to 8.8.8.8 to see archive./is?
2
5
Well it seems like taking some sort of philosophical stand, so rather than wait for that, I just created a static entry on local DNS resolver. "54.36.225.114 archive.is" You could add to your hosts file instead if you don't have local DNS.
2
16
返信を表示
This seems odd - you're blocking a massive amount of users from accessing the site with no explanation of why it may be breaking. Not even a redirect to an http explainer page on archive.is. Took me a while to figure this out and I'm technical. Most people: no hope
28
This deliberate decision on your part is concerning. Is there are problem that arises when you are unable to route some users to the nearest edge? I'm failing to see why this warrants such an extreme retaliation.
15
Extremely disappointed that Cloudflare DNS users continue to be blocked from archive.is - hopefully you guys will get a less stubborn competitor soon!
1
9
web.archive.org is the usual go to
Hey it's been almost two years and this is still an issue. No other site I've encountered refuses to provide failover in this situation. You seem to be quite alone on this.
What are the troubles specifically? I would like to help patch a more graceful approach if possible.
1
6
返信を表示
Just FYI, Firefox now ships with DNS over HTTPS. This uses Cloudflare's resolver so Firefox users can't view your site unless they disable this feature.
See support.mozilla.org/en-US/kb/firef for more info.
1
1
6
Been running into this issue. I knew I could access via Chrome, just wasn't sure why Firefox had a problem. Thanks for the tip!
1
返信先: さん, さん
I really wish you would reconsider blocking CloudFlare DNS. You run a great service and it's annoying to not be able to use it.
3
1
I remember when you used to block Cloudflare DNS requests - and now you're using them as a CND 
1
返信をさらに表示
Twitterを使ってみよう
今すぐ登録して、タイムラインをカスタマイズしましょう。
Googleアカウントでサインイン
電話番号またはメールアドレスで登録
トレンド
いまどうしてる？
COVID-19
ライブ
COVID-19: Keep up with the latest safety and vaccine guidance
![](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="120" height="80"><rect fill-opacity="0"/></svg>)
NBA · トレンド
Dwight
6,885件のツイート
音楽 · トレンド
Post Malone
Post Malone performs at Lollapalooza 2021
3,069件のツイート
![](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24"><rect fill-opacity="0"/></svg>)
Bloomberg Opinion
昨夜
Tick season could be bad this year. Here’s what you need to know
![](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="120" height="81"><rect fill-opacity="0"/></svg>)
The Counter
昨夜
Mexico is phasing out GMO corn and the pesticide glyphosate. The consequences to U.S. trade will be enormous.
![](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="120" height="93"><rect fill-opacity="0"/></svg>)