zlacker

Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

submitted by ikeboy+(OP) on 2019-05-04 18:36:34 | 320 points 194 comments
[source] [go to bottom]

I noticed I couldn't connect to archive.is, eventually I figured out it was an issue with cloudflare DNS, 1.1.1.1. Checking nslookup confirms this:

nslookup archive.is 1.1.1.1 Server: 1.1.1.1 Address: 1.1.1.1#53

Non-authoritative answer: Name: archive.is Address: 127.0.0.4

nslookup archive.is 8.8.8.8 Server: 8.8.8.8 Address: 8.8.8.8#53

Non-authoritative answer: Name: archive.is Address: 94.16.117.236

Cloudflare is returning a localhost address which prevents you from accessing the website.


NOTE: showing posts with links only show all posts
2. derima+x1[view] [source] 2019-05-04 18:50:36
>>ikeboy+(OP)
I remember reading this a while back. It sounded more that archive.is was blocking Cloudflare (or at least not supporting it): https://community.cloudflare.com/t/archive-is-error-1001/182...
3. ikeboy+I1[view] [source] 2019-05-04 18:52:03
>>ikeboy+(OP)
Looks like it's a known issue https://community.cloudflare.com/t/archive-is-error-1001/182..., yet not been fixed for at least a year
4. system+U1[view] [source] 2019-05-04 18:53:36
>>ikeboy+(OP)
Previous discussion here: https://news.ycombinator.com/item?id=17742457
◧◩
5. floati+d2[view] [source] [discussion] 2019-05-04 18:56:00
>>ikeboy+I1
In response to that "unfixed" issue, they noted - in a timely manner, last year - that archive.is is returning bad IPs to them, which is preventing them from serving good IPs:

https://community.cloudflare.com/t/archive-is-error-1001/182...

> Nameservers responsible for archive.is (ben.archive.is, anna.archive.is) are returning answers tailored to the IP address of the requestor.

And indicate that anyone who knows how to contact archive.is can ask them to resolve the issue:

> If you have a contact on the domain owner, you can ask them to fix this.

EDIT: This is knowingly blocked by archive.is. Reasoning and discussion elsewhere in post comments. No need to contact archive.is about it, they’re clearly aware.

10. irtefa+C3[view] [source] 2019-05-04 19:08:55
>>ikeboy+(OP)
This has been a known issue for a while.

Unfortunately, Archive.is has to fix it from their nameservers and we cannot do anything from our side. You can ready more about it here: https://community.cloudflare.com/t/archive-is-error-1001/182...

Disclaimer: I work at Cloudflare

11. miyuru+Q3[view] [source] 2019-05-04 19:10:50
>>ikeboy+(OP)
Cloudflare DNS does not support EDNS Client Subnet[1], so archive.is returns invalid IP address for Cloudflare IPs[2]

[1] https://developers.cloudflare.com/1.1.1.1/nitty-gritty-detai...

[2] https://twitter.com/archiveis/status/1018691421182791680

12. judge2+S3[view] [source] 2019-05-04 19:10:59
>>ikeboy+(OP)
The problem is the archive.is (and other TLDs) server not returning any Good IP if the EDNS client subnet isn't present.

Would like to point out that Cloudflare's resolver is EDNS compliant, it just doesn't send the client subnet.

See: https://twitter.com/archiveis/status/1018691421182791680 (picture of tweet https://aws1.discourse-cdn.com/cloudflare/optimized/3X/8/2/8... )

Based on that tweet, the owner has a personal grudge against Cloudflare and is choosing to return bad results.

◧◩◪◨⬒
15. ikeboy+14[view] [source] [discussion] 2019-05-04 19:13:02
>>akerl_+A3
https://twitter.com/archiveis/status/999788186904576002 claims that cloudflare isn't supporting a protocol that would enable it to work with their servers.
◧◩◪◨⬒
18. Chloru+o4[view] [source] [discussion] 2019-05-04 19:15:46
>>akerl_+A3
>"it seems that archive.is responds to queries from Cloudflare’s systems with an incorrect response."

What makes the response incorrect? I was under the impression that DNS implementations were under no "practical" obligation to return consistent queries to differing requester IP addresses (hence stuff like split-horizon DNS and EDNS: https://developers.google.com/speed/public-dns/docs/ecs )

32. darkho+A6[view] [source] 2019-05-04 19:34:32
>>ikeboy+(OP)
https://developers.cloudflare.com/1.1.1.1/nitty-gritty-detai...

>EDNS Client Subnet

>1.1.1.1 is a privacy centric resolver so it does not send any client IP information and does not send the EDNS Client Subnet Header to authoritative servers.

What does this mean?

◧◩
36. Daniel+i7[view] [source] [discussion] 2019-05-04 19:41:04
>>eastda+d6
An example of something that Cloudflare's approach provides some protection from: http://dnscookie.com/
◧◩◪◨⬒
47. judge2+P8[view] [source] [discussion] 2019-05-04 19:52:12
>>zzzcpa+m7
See the CEO's comment: https://news.ycombinator.com/item?id=19828702

> We’re aware of real world examples where nationstate actors have monitored EDNS subnet information to track individuals, which was part of the motivation for the privacy and security policies of 1.1.1.1.

So it's not just "Cloudflare benefits from pushing anycast" (even if that's part of it).

◧◩◪◨⬒
48. codexo+49[view] [source] [discussion] 2019-05-04 19:53:40
>>zzzcpa+m7
That's not true.

Many setups proxy everything but dns traffic.

That's why this topic is a thing.

https://trac.torproject.org/projects/tor/wiki/doc/Preventing...

◧◩◪◨
49. judge2+d9[view] [source] [discussion] 2019-05-04 19:54:42
>>wolfga+28
This is a problem of the 1^4 resolver not implementing DNAME support (either not a priority, or just in the backlog): https://community.cloudflare.com/t/www-lancaster-ac-uk-not-r...
55. darkho+Ja[view] [source] 2019-05-04 20:07:20
>>ikeboy+(OP)
In Firefox I'm using DNS over HTTPS ( https://mozilla.cloudflare-dns.com/dns-query ) and there is no issue accessing archive.is. Actually I wanted to query archive.is manually but I don't know how to do it in DoH.
◧◩◪◨
56. V99+4b[view] [source] [discussion] 2019-05-04 20:09:46
>>abtinf+O8
I don't know of any particular popular concrete instance, but why is it hard to believe? It's trivial to implement and would be brought to you by the same people who think serving ads for NXDOMAIN is a good idea.

https://www.dnsleaktest.com/what-is-transparent-dns-proxy.ht...

◧◩◪◨⬒⬓⬔⧯▣▦
58. Thorre+Bb[view] [source] [discussion] 2019-05-04 20:13:56
>>ikeboy+n6

    dig @carl.archive.is archive.is A +noedns
responds 134.119.220.26

    curl http://134.119.220.26 -H 'Host: archive.is' -v
responds with HTML of the site.

I'm not a dig expert, but I believe this means it works without EDNS. I think that means archive.is is specifically blocking Cloudflare's servers, not blocking all non-EDNS requests.

◧◩
60. AndyMc+Cc[view] [source] [discussion] 2019-05-04 20:21:08
>>darkho+A6
https://tools.ietf.org/html/rfc7871
◧◩◪◨
62. AndyMc+ed[view] [source] [discussion] 2019-05-04 20:25:41
>>abtinf+O8
https://labs.ripe.net/Members/babak_farrokhi/operator-level-...
◧◩
64. darkho+Xd[view] [source] [discussion] 2019-05-04 20:31:40
>>judge2+S3
Furthermore let's see this report:

https://ednscomp.isc.org/ednscomp/6ed2aca587

EDNS Compliance Tester says that archive.is has some issues.

https://dnsflagday.net

> Minor problems detected! > This domain does not support latest DNS standards.

◧◩
89. logixl+Qq[view] [source] [discussion] 2019-05-04 23:15:34
>>regner+r1
If you don't mind could you look through: https://ooni.torproject.org/about/risks/

And if they sound acceptable run https://ooni.torproject.org/install/

It'll show you more about likely interception of your traffic.

105. rmdoss+jv[view] [source] 2019-05-05 00:16:13
>>ikeboy+(OP)
Archive.is is very interesting. I was checking and they block (by responding back with 127.0.0.3):

- 1.1.1.1

- Neustar DNS

- AdGuard DNS

But they don't block Quad9 or CleanBrowsing that also do not send the EDNS subnet. Very curious way of blocking itself out of the Internet. OpenDNS blocks it (sends to their block page):

https://dnsblacklist.org/?domain=archive.is

Would love to hear from someone from archive.is what is going on.

◧◩◪
106. incomp+lv[view] [source] [discussion] 2019-05-05 00:16:52
>>voldac+Wm
Jurisdiction would include every place where they have a business presence. Their page https://www.cloudflare.com/en-au/about-overview/ lists quite a few international phone numbers, which may or may not correspond with offices and subsidiary companies in those locations.

I assume they'd just have to go along with such legal demands, or withdraw from the relevant country, unless the penalty for not complying was very small.

It will probably become an issue some day. In Australia, for example, courts can issue DNS bans of particular sites to individual ISPs. You can avoid these bans entirely by using a service like Cloudfare DNS.

◧◩
110. HNthro+tx[view] [source] [discussion] 2019-05-05 00:51:34
>>eastda+d6
archive.is is a very important tool in online extremism research and you've taken money from far-right extremists, your explanation for why it's inaccessible seems incomplete.

This is probably where I get banned from Hn but it has to be said - to posture as if you care about end users while in the same breath taking money from extremists and turning over personal identifiable information to far-right outlets like DailyStormer, is disingenuous at best and I can think of other ways to describe it which are less charitable.

You also host and protect 8chan.

https://twitter.com/ncweaver/status/1124091916520497153

https://twitter.com/klarajk/status/1122625367490146304

https://twitter.com/Riverseeker/status/1122612031234945024

https://twitter.com/slpng_giants/status/1123592717341200384

https://twitter.com/NathanBLawrence/status/10562868097418199...

https://twitter.com/NJDemocrat/status/897147112273608705

https://twitter.com/InvestMib/status/1123308004873515015

https://twitter.com/jwz/status/1124415034610860033

◧◩◪
114. syshum+Xx[view] [source] [discussion] 2019-05-05 00:58:39
>>HNthro+tx
This is amusing, They Banned the DailyStormer which I why I will never support them. While I disagree 100% with the DailyStormer it is not up to cloudflare to decide who can and can not speak, who can and can not access the internet.

The concept of Free Speech is the most important right we have as humanity, while I may not agree with some peoples words I will fight for their right to say those words

And do not even come at me with "well they are private company" we impose all kinds of regulations on private companies when it comes to basic human rights like free speech and Free Association for example private companies can not refuse service based on race, sex, age, etc.

yet you WANT them to censor content, censor speech. You want them to apply your left authoritarian world view to legal speech, and yes everything you have cited is LEGAL SPEECH in the USA.

If there are actual threats, True Threats as defined in US law, then the police should be involved and the people arrested. If there is defamation or other illegal speech then the courts should be involved

It should NOT be the position of private companies to regulate speech online

Platform Access Is A Civil Right. https://humanevents.com/2019/05/03/platform-access-is-a-civi...

◧◩◪◨
116. HNthro+qy[view] [source] [discussion] 2019-05-05 01:06:22
>>tdhoot+Px
I'm far from courageous, in fact I'm scared because these groups regularly DoX those who draw attention to this pressing issue:

https://thenextweb.com/opinion/2018/07/17/the-daily-callers-...

http://www.sfweekly.com/news/daily-caller-doxxes-the-s-f-guy...

Journalist like Robert Evans are courageous: https://www.bellingcat.com/news/americas/2019/04/28/ignore-t...

Researchers like Whitney Phillips are courageous https://www.wired.com/story/existential-crisis-plaguing-onli...

I'm just disgusted.

◧◩
117. fapjac+yy[view] [source] [discussion] 2019-05-05 01:08:22
>>eastda+d6
Well no, CloudFlare doesn't get to talk about not "violating the integrity of DNS" after you stopped responding to "any" queries in violation of the standard. You started by doing your own thing and then proposed a change to the standard to fit your business decision. [0]

[0] https://www.rfc-editor.org/info/rfc8482

◧◩
142. sseth+0M[view] [source] [discussion] 2019-05-05 05:11:43
>>z3t4+Zo
Because what you get is often faster, more accurate and more resilient compared to the junk DNS run by most ISPs.

And because most site visits start with a Google search anyway.

And finally, because I am comfortable with their privacy statement : https://developers.google.com/speed/public-dns/privacy

◧◩◪◨⬒
146. dlgeek+bO[view] [source] [discussion] 2019-05-05 06:06:16
>>zimmun+eI
It's a reference to https://www.businessinsider.com/the-daily-stormer-got-pushed...
◧◩◪
147. miyuru+mO[view] [source] [discussion] 2019-05-05 06:10:20
>>notyou+mE
As this is related to CDN, I am gonna leave it here.

The irony is one.one.one.one is marketed as getaway to faster internet, while making CDNs that use GeoDNS slower.

All it takes is a bad route to a far away cloudflare POP to make your internet really slower. Case in point. [1]

I really don't find why no EDNS is considered private, as it only sends the IP subnet.[2] And on IPv6 the IP is far more protected.

If you care that much about privacy, you should be using a VPN.

[1] https://pastebin.com/raw/QnbWXU1a

[2] https://tools.ietf.org/html/rfc7871#section-11.1

◧◩◪
148. sercan+zO[view] [source] [discussion] 2019-05-05 06:18:58
>>Danilo+qn
In my country, government/ISP blocks websites and changes the DNS results of 8.8.8.8 since it is not encrypted. If ISP can create a valid certificate, that browsers trust [1], they may be able to access my Gmail or Github account.

[1] https://www.zdnet.com/article/mozilla-to-chinas-wosign-well-...

◧◩◪◨
149. tambre+GO[view] [source] [discussion] 2019-05-05 06:20:52
>>altfre+RB
I think your accusations are factually incorrect. EDNS was created back in 1999 (RFC2671[0]) waaaaay before Google's 8.8.8.8 in 2009.

And Cloudflare is EDNS-compliant. They simply choose not to enable the optional EDNS extension released in 2016 for sending the client subnet for privacy reasons.

Here's what RFC7871 – Client Subnet in DNS Queries[1] says about itself (emphasis mine):

This document defines an EDNS0 [RFC6891] option to convey network information that is relevant to the DNS message. It will carry sufficient network information about the originator for the Authoritative Nameserver to tailor responses. It will also provide for the Authoritative Nameserver to indicate the scope of network addresses for which the tailored answer is intended. This EDNS0 option is intended for those Recursive Resolvers and Authoritative Nameservers that would benefit from the extension and not for general purpose deployment. This is completely optional and can safely be ignored by servers that choose not to implement or enable it.

As far as I know, the standard practice, before this optional EDNS extension was to do GeoDNS based on the resolver's IP. This works just fine, including in the case of Cloudflare, since they've got 150+ POPs with each resolving on their own. That's higher density than most CDNs.

[0]: https://tools.ietf.org/html/rfc2671

[1]: https://tools.ietf.org/html/rfc7871

◧◩◪◨
150. Smyler+nP[view] [source] [discussion] 2019-05-05 06:35:52
>>wolfga+28
In what way doesn't it work? This is with my ISP's DNS (using which I can visit https://www.lancaster.ac.uk/ in a browser):

  $ host -t a lancaster.ac.uk
  lancaster.ac.uk has address 148.88.65.80
and this is with Cloudflare's:

  $ host -t a lancaster.ac.uk 1.1.1.1
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  lancaster.ac.uk has address 148.88.65.80
Looks the same to me.
◧◩◪◨⬒
153. syshum+8Q[view] [source] [discussion] 2019-05-05 06:55:14
>>zimmun+eI
https://blog.cloudflare.com/why-we-terminated-daily-stormer/
◧◩◪◨
158. lmb+1T[view] [source] [discussion] 2019-05-05 08:02:36
>>fapjac+Ly
What do you mean with this? Refuse ANY is now a proposed RFC https://datatracker.ietf.org/doc/rfc8482/ How is that a band aid?
◧◩◪◨⬒
168. teclea+ZW[view] [source] [discussion] 2019-05-05 09:47:13
>>notyou+QI
Google Cloud CDN has been GA since 3 years ago:

https://cloud.google.com/cdn/docs/release-notes#june_27_2016

◧◩◪◨⬒
169. stevek+uZ[view] [source] [discussion] 2019-05-05 10:39:00
>>wolco+Xn
Has some notes on the topic:

https://en.wikipedia.org/wiki/Archive.today#Finland

◧◩◪◨⬒⬓
172. maccar+L41[view] [source] [discussion] 2019-05-05 12:27:42
>>syshum+pQ
I don't have an answer to who should be the arbiter, but:

> Free Speech is the most powerful tool Minorities and oppressed people through out the world have to end their oppression,

So in order to protect the opressed, we should allow their opressors an equal platform to share their totalitarian views?

The other side(what we currently have) is equally as bad, if not worse. Right now you have a situation where the BBC in the name of "fairness" gives equal air time to a political party who only exist as a protest vote, and they allow for climate change denier to air their views against scientists. Public debate doesn't work based on facts, it works based on emotions, and it doesn't matter how nuanced or level headed your response is, "think of the children" or "the government is trying to suppress our rights" are emotional arguments that consistently Trump facts and reason. Free speech isn't a right for you to have a platform to voice your opinion, it's a right to not have your opinion be suppressed by the government.

I don't have a solution, but at some point you have to accept that tolerance of intolerance is intolerance, and when we're talking about a single incident of a platform that claims Marital Rape is ok [0],and that murdering 50 people because of their religion is "a prank" [1], they are objectively the opressors, not the opressed.

[0] https://dailystormer.name/some-states-want-to-prevent-husban...

[1] https://dailystormer.name/the-difference-between-a-mosque-sh...

◧◩◪◨⬒⬓⬔
176. syshum+E81[view] [source] [discussion] 2019-05-05 13:30:12
>>maccar+L41
>>So in order to protect the opressed, we should allow their opressors an equal platform to share their totalitarian views?

yes, for many reasons. One Should not be celebrating Moving the Cliff of Censorship on the bias of "Dangerous Individuals" like Facebook recently did. [2]

>Free speech isn't a right for you to have a platform to voice your opinion, it's a right to not have your opinion be suppressed by the government.

100% incorrect, Free Speech is a social concept that is often codified into law as through out history governments are the ones that often use the power of censorship to silence dissent, however threats by government is NOT the only threat to free speech.

Free Speech is a cultural value first, it has become a legal articulation based on that cultural value. [2] Platform Access Is A Civil Right, You should now have the same right to speak on Facebook, Twitter, and Instagram that you do in a public park.[0]

If you would not celebrate government censoring opinions you dislike why would you celebrate corporations doing it?

>>I don't have a solution, but at some point you have to accept that tolerance of intolerance is intolerance

The US Supreme Court disagrees with you, you can not fight intolerance by suppression. it has never worked in all of history, it only makes the extremism more extreme and violent. One can make the strong case that the more society pushes these people out of the sunlight the more violent they become, and if they allowed the modern public square, where their idea's would be challenged, debated and debunked there is a high probity there would be LESS violence.

Censorship does nothing but drive extremism under ground allowing it to fester, become more extreme, and then you get violence. This is also true for other forms of Censorship. Take for example the recent bills to "stop human trafficking" by censoring platforms and making them liable for it. Did it actually stop any human trafficking... No, all it did was drive it under ground making it harder for law enforcement to track and stop, while suppression lots of legitimate speech, had massive negative effects on voluntary sex workers, and untold other unintended consequences. This censorship was a net negative both in its stated goal, and for freedom in general. It accomplished nothing but taking the rights away from people.

Once your Nation has a "Chief Censor" [1] you know you have gone away from anything that could be considered Free Speech

[0] https://humanevents.com/2019/05/03/platform-access-is-a-civi...

[1] https://youtu.be/QH_IZnKzqKA?t=68

[2] https://www.youtube.com/watch?v=GOwJz1p6aag

◧◩◪◨⬒⬓⬔
181. meowfa+Nj1[view] [source] [discussion] 2019-05-05 15:52:11
>>maccar+L41
>So in order to protect the opressed, we should allow their opressors an equal platform to share their totalitarian views?

Yes. That's one of the founding principles of America. Cloudflare is a common carrier like a telco, not a hosting provider. The content on websites that use them as a CDN shouldn't be paid attention to by Cloudflare one way or another, as long as it's legal. This is their position, and it's the correct and most moral one. You also seem to be missing the fact that Cloudflare famously banned Daily Stormer; the only time they've ever banned any website: https://blog.cloudflare.com/why-we-terminated-daily-stormer/

The best way to empower extremists is by trying to stamp them out. You can never, ever win when your primary weapon is censorship. Fascism thrives and festers in darkness.

◧◩
182. iliken+Mn1[view] [source] [discussion] 2019-05-05 16:46:14
>>eastda+d6
If you're for integrity of DNS, why did you suspend the free speech of the admittedly bigoted, hateful neonazis on dailystormer?

https://blog.cloudflare.com/why-we-terminated-daily-stormer/

"Earlier today, Cloudflare terminated the account of the Daily Stormer. We've stopped proxying their traffic and stopped answering DNS requests for their sites. We've taken measures to ensure that they cannot sign up for Cloudflare's services ever again."

I'll keep using non-logging, encrypted OpenNIC servers, since you seem to selectively censor instead of only blocking terrorists and cp.

◧◩◪◨⬒⬓
186. fapjac+fR2[view] [source] [discussion] 2019-05-06 13:43:57
>>syshum+0Q
Actually it's the opposite. It's the newer people that are this way [0], for in my day, most people didn't even trust computers, let alone buying things with a computer, or always carrying an always-connected computer with a microphone and multiple cameras in their pocket.

[0] https://www.pewsocialtrends.org/2019/01/17/generation-z-look...

◧◩◪◨⬒
189. ff317+Ff3[view] [source] [discussion] 2019-05-06 16:18:39
>>lmb+1T
Just for another voice in this sub-discussion: I'm an authdns software implementer ( https://github.com/gdnsd/gdnsd ) with no connection to Cloudflare, and I like Refuse ANY. It's maybe hard to see all the issues with traditional ANY clearly unless you're implementing this stuff, but IMHO RFC 8482 is a really good path forward that I'm supportive of and have also implemented.
◧◩◪
191. jolmg+yL6[view] [source] [discussion] 2019-05-07 23:14:49
>>dredmo+2K
Interesting, I thought archive.is was an alternate domain of the Internet Archive, but it seems they are completely different people[1].

[1] https://en.wikipedia.org/wiki/Archive.today

◧◩◪◨⬒
194. fapjac+0Xa[view] [source] [discussion] 2019-05-09 17:45:50
>>lmb+1T
Well, I can't say I didn't anticipate it happening exactly like this, with someone from Cloudflare trying to retcon "the ANY query episode" by linking to the proposal drafted after the fact. As though a formal "here is our proposed change" document somehow magically excuses the fact that Cloudflare did "violate the integrity of DNS" in its unilateral decision to abandon parts of the DNS specification in favor of its own modifications in order to cut operating costs by reducing the workload on its servers. [0]

Your boss is talking about not "violating the integrity of DNS" and presents this case where upstream archive.is name servers return unexpected data. He proposes that CloudFlare cannot "just fix it" because doing so "would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service". However, Cloudflare chose to "just fix it" back then by "slapping a bandaid" on something your team saw as a problem instead of abiding by the proper change process. And Cloudflare did so not because of some critical security flaw, but as a cost-cutting measure.

Even if we limit what it means to "violate the integrity of DNS" to the first definition mentioned above (and completely ignore this second definition), Cloudflare "slapped a bandaid" on a PR problem it had a couple of years ago and decided to "just fix it" and "block a domain" by removing the domain and its assets from Cloudflare's infrastructure. [1]

Cloudflare has "violated the integrity of DNS" on more than one occasion using more than one of its own definitions.

Cloudflare "MUST" either adhere to the specification and its change process, or not adhere to the specification and its change process. Cloudflare "CANNOT" choose for both of these statements to be true, and one of them constitutes "violating the integrity of DNS".

[0] https://blog.cloudflare.com/deprecating-dns-any-meta-query-t...

[1] https://blog.cloudflare.com/why-we-terminated-daily-stormer/

[go to top]