10 ms·
Does Cloudflare’s 1.1.1.1 DNS Block Archive.is? (2019)
- wkat4242 3y agoMaybe they need it to route the traffic to the right CDN? That kinda would make sense. While I'm very privacy conscious, I don't really see the benefit to hiding my region in the DNS request. Because the very next step after the DNS is my browser making a request to their webserver, at which time they will have my actual complete IP anyway.
- philwelch 3y agoThis is actually addressed in the original HN comment the post links to (https://news.ycombinator.com/item?id=19828702 https://news.ycombinator.com/item?id=19828702): > EDNS IP subsets can be used to better geolocate responses for services that use DNS-based load balancing. However, 1.1.1.1 is delivered across Cloudflare’s entire network that today spans 180 cities. We publish the geolocation information of the IPs that we query from. That allows any network with less density than we have to properly return DNS-targeted results.
- eastdakota 3y agoAnd today it’s over 250. And the only site I’m aware of that objects to us protecting user privacy by making EDNS more private is this one. ¯\_(ツ)_/¯
- mikecoles 3y ago"Protecting user privacy", from the largest MITM attackers on the internet, is laughable.
- freedomben 3y ago> from the largest MITM attackers If that were true, there's a lot of really stupid people throwing away their money by paying CF to hack them.
- dmvdoug 3y agoRight, the site full of nerds who think archive.is and co. is a cool toy. Dilemma! ;)
- wkat4242 3y agoYeah but if the site standardized on EDNS to get this information, it's rather difficult to do something different just for Cloudflare.
- p1mrx 3y agoedns-client-subnet only provides an IP address; the receiving CDN still needs to geolocate it. So the main difference is that Cloudflare's servers need to be present in the IP geolocation database. Given their prevalence, they're probably in most of them already.
- jrockway 3y agoeastdakota's original comment covers this. The DNS request isn't encrypted, so anyone with control over the network (upstream ISPs via warrants) can use this information to figure out who is attempting to visit. ("Someone is resolving example.com" is less information than "someone in LA is resolving example.com") Meanwhile, the actual HTTPS connection leaks less information. If the website is hosted on a CDN or cloud provider, then someone monitoring the IP traffic only knows that you're visiting something hosted by that CDN. ("The target is visiting a Cloudflare-hosted site" is less information than "The target is visiting example.com") So, there is a slight information leak by sending the geolocation information. On the other hand, it's possible this doesn't matter. The client might not encrypt the host it's trying to visit. Nation states can correlate packet timing. So if someone really wants to know, they'll probably figure it out. (This is always a risk with things like Tor. If the government is monitoring your connection and some target website's connection, and you are sending a lot of packets at the same time they're receiving a lot of packets, you can guess who is talking to who.)
- cortesoft 3y ago> If the website is hosted on a CDN or cloud provider, then someone monitoring the IP traffic only knows that you're visiting something hosted by that CDN. This isn't true, because the request leaks the hostname in the handshake via SNI: https://en.wikipedia.org/wiki/Server_Name_Indication https://en.wikipedia.org/wiki/Server_Name_Indication
- pigeonhole123 3y agoEncrypted SNI has been in the works for a long time: https://www.cloudflare.com/en-gb/learning/ssl/what-is-encrypted-sni/ https://www.cloudflare.com/en-gb/learning/ssl/what-is-encryp...
- cortesoft 3y agoRight, but it isn't standard yet still.
- jeroenhd 3y agoI've talked to some people working for the .nl TLD. They collect logs on DNS requests for every .nl domain to mine data about phishing websites and online scams. They're not using the EDNS information as far as I know (that would be very very illegal) and I don't know what the introduction of the GDPR has done to their research, but TLDs not limited by privacy laws such as American companies can do whatever they want. It's not just the website's DNS server that received your subnet information; it's every single location in the chain of DNS resolvers. That includes TLD servers run by data mining companies. Does Verisign need to know that 2001:2345:6789::abcd is looking for news.ycombinator.com? With caching in place these methods of data gathering aren't all-encompassing, but if you visit some new or uncommon domains you'll be more likely to become part of the dataset.
- Arnavion 3y ago>Does Verisign need to know that 2001:2345:6789::abcd is looking for news.ycombinator.com? Verizon wouldn't know that even with ECS, because ECS only needs to include the subnet prefix of the length that the client (Cloudflare's recursive resolver in this case) is willing to give out. There is no benefit and only harm to the client if it gives out the whole IP, and indeed it is called out as a bad idea in the ECS RFC.
- deleted 3y ago[deleted]
- lol768 3y agoPrevious discussions: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1) https://news.ycombinator.com/item?id=19828317 https://news.ycombinator.com/item?id=19828317 - This particular discussion includes a comment from Cloudflare's CEO, referenced in the article: https://news.ycombinator.com/item?id=19828702 https://news.ycombinator.com/item?id=19828702 Why does 1.1.1.1 not resolve archive.is? https://news.ycombinator.com/item?id=21155056 https://news.ycombinator.com/item?id=21155056 - StackExchange question, on the subject Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (2019) https://news.ycombinator.com/item?id=28495204 https://news.ycombinator.com/item?id=28495204 - Discussion of this blog post
- 38 3y agosince your formatting is weird, here is the direct link to the stack exchange question: https://webapps.stackexchange.com/questions/135222 https://webapps.stackexchange.com/questions/135222
- 7sovaren 3y agoHmm, no clue but if i ask 1.1.1.1 for the a record for archive.is i get 89.253.237.217 asking the office DNS the same question i get 51.38.69.52, asking 9.9.9.9 it gives me the same IP as the office DNS. Finaly asking google or 8.8.8.8 i also get 51.38.69.52 So i think their record is borked.
- bombcar 3y agoSupposedly Cloudflare uses a feature of DNS archive.* doesn't like, or vice versa. Nobody cares; the reality is if you use CF DNS, shit don't work.
- nuker 3y agoIm using iCloud Private Relay, and it affects me.
- almost_usual 3y agoI’m using iCloud Private Relay and it works fine.
- kalleboo 3y agoI use iCloud Private Relay and it only affects me over IPv6. Disabling either private relay or ipv6 "fixes" it
- mdasen 3y agoiCloud Private Relay uses a variety of third parties for their network connectivity. If it's working fine, you might be going out via Fastly or someone else. The person who it's not working for is likely getting Cloudflare. With iCloud Private Relay, it sometimes works for me and sometimes doesn't depending on which CDN's system I'm using at the time.
- jeroenhd 3y agoIt's not just Cloudflare, it's any DNS resolver that doesn't implement EDNS extensions. If you (or the company you work for) run a recursive resolver that doesn't submit such data, you'll run into the same issues. I've switched to archive.org because archive.* is broken. For stuff that .org doesn't have, there's always the Tor version. The Tor address seems to be more responsive as well, so that's nice.
- cj 3y agoComment from Cloudflare CEO from 2019: https://news.ycombinator.com/item?id=19828702 https://news.ycombinator.com/item?id=19828702 Surfacing here for people who like to read comments before clicking through to the article. TLDR: the site owner was returning wrong DNS responses for people using Cloudflare's 1.1.1.1 DNS service because the site owner doesn't like Cloudflare.
- lolinder 3y agoThey still are! I recently switched to Cloudflare DNS and noticed all the archive links people post on HN stopped working.
- photonerd 3y agoAnd the reason they do that is quite reasonable. CF is just being a pain
- flutas 3y ago> the site owner was returning wrong DNS responses for people using Cloudflare's 1.1.1.1 DNS service because the site owner doesn't like Cloudflare. Or you can try to not imagine everyone as hating everything and read the other comment in here posting the archive.* side of the story. > There have been numerous attacks where people upload illegal content (childporn or isis propaganda) and immediately reported to the authorities near the IP of the archive. It resulted in ceased servers and downtimes. I just have no time to react. So I developed sort of CDN, with the only difference: DNS server returns not the closest IP to the request origin but the closest IP abroad, so any takedown procedure would require bureaucratic procedures so I am getting notified notified and have time to react. > But CloudFlare DNS disrupts the scheme together with all other DNS-based CDNs Cloudflare is competing with and puts the archive existence on risk. I offered them to proxy those CloudFlare DNS's users via their CDN but they rejected. Registering my own autonomous system just to fix the issue with CloudFlare DNS is too expensive for me.
- jeroenhd 3y agoI don't know for sure what's going on with the DNS. I know the archive.* website messes with Cloudflare's DNS results because they don't know how to set up anycast, but when I use some external tool to look up the right address and hardcode that I still get either a TLS error or "hello world". archiveiya74codqgiixo33q62qlrqtkgmcitqx5u2oeqnmn5bpcbiyd.onion still works fine if you don't want to share your geolocation information with every DNS server in the recursive resolver chain.
- freedomben 3y agoCloudflare CEO Matthew Prince answered this directly on HN: https://news.ycombinator.com/item?id=19828702 https://news.ycombinator.com/item?id=19828702 Most relevant piece but the whole comment is worth a read: > 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. Honestly it's that type of thing (the frankness, the presence on HN, willingness to participate, the principled stand on privacy) that got me into Cloudflare products. I now generate hundreds per month in revenue for them and that will likely be thousands in the next year or two. His time/effort on HN directly led to customer acquisition and revenue. That said I do worry about the incentives Cloudflare has to their big customers. CF is a great tool for site owners, but like any tool has the potential to be a great evil (against the user) if the principles ever wane. It's already being used by a lot of sites to make life a living hell for people behind a VPN. As a site owner I absolutely get it: practically zero of my legitimate traffic comes from VPNs (our main demographic tend to skew older and much less technical than the average consumer), but all of the automated attacks against me do. Balancing freedom and rights is hard, but I deeply appreciate the thoughtfulness and principles that CF has displayed over the years.
- mschuster91 3y ago[flagged]
- hk1337 3y agoSeems like a good reason not to be exclusive with a single DNS service.
- wkat4242 3y agoI don't think this will help. It still returns an IP, it's just wrong. Setting a second DNS won't help if the first one returns a response.
- diogocp 3y agoThis is obviously not Cloudflare's fault, but I wonder why they don't just mask their identity (e.g. by using a random AWS IP address) when querying archive.is? AFAICT this wouldn't "violate the integrity of DNS and the privacy and security promises we made to our users" and would solve a big pain point of using 1.1.1.1.
- freedomben 3y agoI'm not affiliated with CF at all, but if I were I would oppose that idea on a couple levels. Philosophically I think that lacks respect for the site owner and it would be wrong to deceive them and go against their wishes. Pragmatically that sounds like a giant maintenance pain in the ass to manage, and not worth the time/money to make somebody's site work who actively doesn't want it to work.
- eastdakota 3y agoWe’ve tried. The owner of Archive.is actively monitors and then returns bad results. This is true even if we recurse through another recursor. It’s a very odd hill to die on.
- dataflow 3y agoI think I'm missing something, but is there a way you can pass along some some sort of vague location info for caching purposes without revealing too much? From their tweet they mentioned even continent level information isn't available, which I can understand. Is there really no middle ground that works here?
- afavour 3y agoFrom another post the CEO made it sounds like they could do a bunch of things but don’t think they should. Which I understand. Once you start adding workarounds for specific domains I can imagine the whole thing spiralling quickly. The owner of archive.is doesn’t want the traffic, CF probably shouldn’t move heaven and earth in response.
- kalleboo 3y agoLately I've run into the issue that they're also blocking iCloud Private Relay. Although for some reason the block is only affecting me over IPv6, if I disable v6 it works, which led me to waste a bunch of time debugging. The seemingly anti-privacy blocks by archive and the fact that nobody knows who funds this extremely popular service has led me down conspiratorial thought patterns.
- TechBro8615 3y agoCloudflare is one of the operators of egress nodes for iCloud Private Relay, along with Akamai and Fastly and maybe some others (IIRC). So you probably have issues with Archive.is when you're connected through Cloudflare. Although I'm not sure how DNS resolution works on private relay (since it's the DNS server rather than the egress proxy that causes the issue - but if the egress proxy is making the DNS requests then that would explain it).
- kalleboo 3y agoAh that would explain it!
- saveferris 3y agoI have the same issue and just now found it was because of Private Relay. I did not connect the fact that I had no issues accessing archive.is when I had a VPN on - which disables Private Relay. Since they got a location, not my location but a location they were hunky dory.... I saw this post and tried it with and without Private Relay and sure enough, turning it on is the issue. Good to know.... Edit: I updated Private Relay to "Maintain general location" for IP Address Location Settings and archive.is loads fine. Second Edit: Maybe not, it all works now and I think it is either session or cache. I got to play around with it
- TechBro8615 3y agoDoes enabling a VPN disable private relay or does it tunnel to the VPN through private relay? For some reason I have it in my head that it "double wraps" the traffic but I've never actually confirmed that for a fact.
- electroly 3y agoIntransigent maintainers are such an irritating problem. Any time a maintainer has some strongly-held beliefs or goals that supersede their desire to serve users, you've got a ticking time bomb. When the two clash, they'll decline to serve users in order to serve their strongly-held belief instead. We see it time and time again.
- ninjagoo 3y agoThis case might not be one of an intransigent maintainers. Check out Stavros' note [1] https://news.ycombinator.com/item?id=36971650 https://news.ycombinator.com/item?id=36971650
- electroly 3y agoIndeed, they mention that the proper solution is to get their own AS but that it's too expensive (this is what other major websites do). Cloudflare argues that they are protecting user privacy by truncating the EDNS responses, and I believe it's commonly agreed that they're right that this move does so. Archive.is says explicitly that they want this because it's cheaper than an alternative that is available to them. The cost of running an AS is disputed elsewhere in this HN thread. To me it seems clear that Cloudflare has the moral upper hand.
- whoopdedo 3y agoAre you talking about Archive.is or Cloudflare? Answer: "Yes."
- electroly 3y agoI do believe both parties see the other this way. Archive.is believes that Cloudflare can simply provide the full EDNS data, and they're technically right. But Cloudflare won't budge because they believe this is hostile to user privacy. I haven't heard a counterargument that Cloudflare is wrong about this. Cloudflare believes that Archive.is can simply live without the EDNS data, and they're technically right. But Archive.is won't budge because they believe it prevents their abuse prevention techniques. They mention that owning their own AS would solve the problem but that's too expensive.[1] Blame is in the eye of the beholder, but it seems to me that Archive.is should find alternative abuse prevention techniques like other websites do. Cloudflare has an argument based on privacy. Archive.is has an argument based on the proper solution being too expensive. The expense of running an AS is disputed in this HN thread.[2] [1] https://news.ycombinator.com/item?id=36971650 https://news.ycombinator.com/item?id=36971650 [2] https://news.ycombinator.com/item?id=36977654 https://news.ycombinator.com/item?id=36977654
- adithyassekhar 3y agoCloudflare is also hurting peering and ggc to Google on my ISP. When I use google dns, opendns or even my isp's own dns, the ip I get for example, googlevideo.com resolves to my isp's cache. But with cloudflare it gives my a google ip and I get no cache benefits. Also, anecdotal evidence, uploading and downloading large files to Google Drive and some other websites is significantly faster when I use google dns or opendns. I'm not sure how that works, but maybe the server's returning an ip my isp can't route to in a fast way? My isp is notorious for having bad routes.
- ChrisArchitect 3y ago(2019) Did this need to be posted again when it was discussed and answered already?
- Goz3rr 3y agoFor me it worked for a while, and has broken again earlier this year.
- stavros 3y agoI talked to the maintainer of archive.is years ago, they said this (hopefully they won't mind me posting): > There have been numerous attacks where people upload illegal content (childporn or isis propaganda) and immediately reported to the authorities near the IP of the archive. It resulted in ceased servers and downtimes. I just have no time to react. So I developed sort of CDN, with the only difference: DNS server returns not the closest IP to the request origin but the closest IP abroad, so any takedown procedure would require bureaucratic procedures so I am getting notified notified and have time to react. > But CloudFlare DNS disrupts the scheme together with all other DNS-based CDNs Cloudflare is competing with and puts the archive existence on risk. I offered them to proxy those CloudFlare DNS's users via their CDN but they rejected. Registering my own autonomous system just to fix the issue with CloudFlare DNS is too expensive for me. When I proposed using the DNS server's IP instead, they said: > It did not work initially because they have global planetwide cache. > 1. Someone resolves domain from Brazil. > 2. Website's DNS get request from Cloudflare Brazil DC. > 3. The result is replicated to other Cloudflare DCs > 4. Some from Turkey resolves same domain and get the cached value > It could be worked around by setting tiny TTL, which would slowly end up in consistent results, but... After "I’ve proposed we just fix it on our end .." all requests for 7 archive.* domains are sent from Symantec USA IP
- codetrotter 3y agoThis makes a lot of sense, and this comment should be higher. The other comments that only present the Cloudflare side of the situation make it sound like the archive.is owner was being unreasonable, but as we see there is more to it! I personally tried to use 1.1.1.1 as my resolver a couple of years ago but I use archive.is a lot. Regardless of who is “at fault”, not being able to access archive.is is a dealbreaker for me so I quickly stopped using 1.1.1.1 But Cloudflare has a lot of other things that work well for me.
- flangola7 3y agoWow. archive.is proposed a perfectly good solution and CF shot it down.
- fastball 3y agoI'm using 1.1.1.1 and I can go to archive.is – is this still relevant?
- mellosouls 3y agoTangentially, various network providers (eg. some mobile networks) block access to some archive sites (particularly the Internet Archive as it's the most well known one) on the basis of them containing adult/pirated content.
- waithuh 3y agoWhile archive.is' reaction is questionable (and even then, its their own server and can do whatever they want with it) this blog post is throughout Cloudflare advertising. The CEO used the scenario to their advantage very cleverly, but this blog post could describe all of that without constantly reminding how wonderful CF is.
- pessimizer 3y agoOr, they could do it while constantly reminding people how wonderful Cloudflare is, just because they want to. I'm not sure why supposed to be wrong to honestly advertise.
- tiltowait 3y agoMany people think any form of advertising is evil. Though incorrect, it's perhaps a predictable reaction to the pervasive and genuinely morally bankrupt advertising we're inundated with on a regular basis.
- rejectfinite 3y agoI switched to https://controld.com/free-dns https://controld.com/free-dns Can also do DNS adblock! :)
- ishanjain28 3y agoI am in India, using 1.1.1.1 over DoT and it appears to be working okay. I am served IP addresses with relatively short TTLs (1-5minutes) that are in Moscow and North Holland.
- Goz3rr 3y agoIf you're using a Pi-hole for your DNS (or anything else using dnsmasq I suppose), I worked around the issue by creating /etc/dnsmasq.d/02-archive.is.conf (with a Docker bind mount in my case) with the following content: server=/archive.today/8.8.8.8 server=/archive.today/8.8.4.4 server=/archive.ph/8.8.8.8 server=/archive.ph/8.8.4.4 server=/archive.is/8.8.8.8 server=/archive.is/8.8.4.4 server=/archive.li/8.8.8.8 server=/archive.li/8.8.4.4 server=/archive.vn/8.8.8.8 server=/archive.vn/8.8.4.4 server=/archive.fo/8.8.8.8 server=/archive.fo/8.8.4.4 server=/archive.md/8.8.8.8 server=/archive.md/8.8.4.4 server=/archive.to/8.8.8.8 server=/archive.to/8.8.4.4 This way you use 1.1.1.1 for everything, except the domains listed above where it uses Google DNS instead.
- croes 3y agoAnd you leak your location, don't you?
- therealmarv 3y agoas does your IP. Where is the win?
- ploxiln 3y ago... less than when you connect to the archive.is servers for http requests
- akira2501 3y agoIt's like a cab driver being overly concerned that when I arrive at my destination, they will be able to know who I am just by looking at me. "Yea.. thanks dude. Just.. drive the car, will ya?"
- Goz3rr 3y agoThe problem is that there are more parties than you, your DNS server (the cab driver) and your destination (the website). The cab driver might have to ask a number of other people how to get to the destination. Your DNS server probably doesn't have the exact record for you at the ready, but it does know another DNS server that gets you closer to an answer. That's how recursive DNS works and it might happen a few times before you actually get to a result. With ECS now every DNS server in this chain knows 12.45.56.x wanted to visit hacker news.
- babypuncher 3y agoIf Archive.is doesn't want to respond to valid DNS requests then I don't see a reason to use or support them.
- therealmarv 3y agoAny alternatives which support DoH, DoT, DoQ and do not think they need to reinvent (E)DNS ? Google works but I want to keep a little distance from them. Also no big fan of Quad9. So what else to use and which is distributed World Wide?
- silisili 3y agoI use and pay for nextdns, and am a huge fan.
- brirec 3y agoOne way you can get around this and still use 1.1.1.1 for most sites would be to use a local recursive resolver that supports domain name-based upstream overrides such as dnsmasq, and setting that as your local resolver. You can run dnsmasq on anything that can run arbitrary services e.g. on your local workstation, or on your router if it is open enough, or even on something like Termux probably.
- obituary_latte 3y agoStrangely, I get a Russian IP address for an answer when I query 1.1.1.1 for archive.is: ┌─(~/Projects/malware/triangulation)(ruby-2.5.0)────────────────────────────────────────────────────────────────────(c@c:s001)─┐ └─(12:32:59)──> nslookup archive.is 1.1.1.1 ──(Wed,Aug02)─┘ Server: 1.1.1.1 Address: 1.1.1.1#53 Non-authoritative answer: Name: archive.is Address: 89.253.237.217 ┌─(~/Projects/malware/triangulation)(ruby-2.5.0)────────────────────────────────────────────────────────────────────(c@c:s001)─┐ └─(12:38:12)──> nslookup archive.is 1.0.0.1 ──(Wed,Aug02)─┘ Server: 1.0.0.1 Address: 1.0.0.1#53 Non-authoritative answer: Name: archive.is Address: 89.253.237.217 ┌─(~/Projects/malware/triangulation)(ruby-2.5.0)────────────────────────────────────────────────────────────────────(c@c:s001)─┐ └─(12:38:14)──> whois 89.253.237.217 ──(Wed,Aug02)─┘ % IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: whois.ripe.net inetnum: 89.0.0.0 - 89.255.255.255 organisation: RIPE NCC status: ALLOCATED whois: whois.ripe.net changed: 2005-06 source: IANA # whois.ripe.net inetnum: 89.253.232.0 - 89.253.239.255 org: ORG-RL31-RIPE netname: RU-RUSONYX-NET6 descr: Network for Rusonyx infrastructure country: RU mnt-lower: MNT-RUSONYX mnt-routes: MNT-RUSONYX admin-c: VZ1716-RIPE admin-c: VZ1717-RIPE tech-c: VZ1716-RIPE status: ASSIGNED PA mnt-by: MNT-RUSONYX created: 2018-10-10T09:53:33Z last-modified: 2018-10-16T12:37:40Z source: RIPE # Filtered organisation: ORG-RL31-RIPE org-name: Rusonyx, Ltd. country: RU org-type: LIR address: 5th st. Yamskogo Polya, 9, office 19 address: 125040 address: Moscow address: RUSSIAN FEDERATION phone: +74951370701 fax-no: +74951370701 mnt-ref: RIPE-NCC-HM-MNT mnt-ref: MNT-RUSONYX mnt-by: RIPE-NCC-HM-MNT mnt-by: MNT-RUSONYX abuse-c: AD11015-RIPE created: 2006-08-18T09:59:51Z last-modified: 2022-10-06T11:18:08Z source: RIPE # Filtered person: Viktor Zverkov address: P.O. Box 19 address: 127137, Moscow, Russia address: Rusonyx ltd. phone: +7 495 5089959 nic-hdl: VZ1716-RIPE mnt-by: MNT-RUSONYX created: 2017-09-20T11:29:16Z last-modified: 2022-07-05T14:00:10Z source: RIPE person: Viktor Zaytsev address: P.O. Box 19 , Russia address: 127137, Moscow address: Rusonyx ltd. phone: +7 495 5089959 nic-hdl: VZ1717-RIPE mnt-by: MNT-RUSONYX mnt-by: AM65535-MNT created: 2017-09-20T11:54:54Z last-modified: 2018-08-02T17:21:31Z source: RIPE % Information related to '89.253.232.0/21AS41535' route: 89.253.232.0/21 descr: RUSONYX-RU origin: AS41535 mnt-by: MNT-RUSONYX created: 2017-11-24T09:34:37Z last-modified: 2017-11-24T09:34:37Z source: RIPE % This query was served by the RIPE Database Query Service version 1.107 (DEXTER) Not sure why this would be happening (looks like at least one other person in the thread is seeing same result).
- wnevets 3y agoOh is that why archive.is links on HN will fail for me sometimes?
- msravi 3y agoNextdns: How we made DNS both fast and private with ECS[0] Cloudflare sends the closest city from where the request was made which ought to be sufficient to optimize for a cdn I guess? Appears that archive.is doesn't have a locus standii in this debate... > EDNS IP subsets can be used to better geolocate responses for services that use DNS-based load balancing. However, 1.1.1.1 is delivered across Cloudflare’s entire network that today spans 180 cities. We publish the geolocation information of the IPs that we query from. That allows any network with less density than we have to properly return DNS-targeted results. 0. https://medium.com/nextdns/how-we-made-dns-both-fast-and-private-with-ecs-4970d70401e5 https://medium.com/nextdns/how-we-made-dns-both-fast-and-pri...
- Arnavion 3y ago>Cloudflare sends the closest city from where the request was made which ought to be sufficient to optimize for a cdn I guess? Appears that archive.is doesn't have a locus standii in this debate... https://news.ycombinator.com/item?id=36973056 https://news.ycombinator.com/item?id=36973056 >>all requests for 7 archive.* domains are sent from Symantec USA IP It might be that the archive.is only lies to that IP, which would explain why many users in this thread say that archive.is does resolve correctly for them with 1.1.1.1
- 8chanAnon 3y agoSeems like this is no longer relevant. I just tried a DNS lookup via Cloudflare and I got 89.253.237.217.
- lolinder 3y agoI'm seeing that now too. It might have changed in the last 4 hours, or maybe the behavior is cyclical for some reason. I posted this article after running into it repeatedly over the last few weeks since switching to Cloudflare DNS. I wonder if one party or the other actually made a change in response to this hitting the front page again?
- tredre3 3y agoThe behaviour is cyclical. It has been for years, really. It starts resolving every now and then, but rarely for long and I doubt this time is any different. I don't think archive.is blocks CF based on their IPs, so they must have some heuristic in place to defect bogus EDNS. Perhaps sometimes that heuristics fails?
- below43 3y agohttps://archive.is/hpKIB https://archive.is/hpKIB
- News-Dog 3y agoarchive.today or archive.is : https://en.wikipedia.org/wiki/Archive.today https://en.wikipedia.org/wiki/Archive.today archive.today - FAQ : https://archive.md/faq https://archive.md/faq archive.today - wiki : https://wiki.archiveteam.org/index.php/Archive.today https://wiki.archiveteam.org/index.php/Archive.today archiveteam wiki : https://wiki.archiveteam.org/ https://wiki.archiveteam.org/ Tumblr : https://archive-is.tumblr.com/ https://archive-is.tumblr.com/ Twitter : https://twitter.com/archiveis https://twitter.com/archiveis archive.today archive.ph archive.is archive.li archive.vn archive.fo archive.md archiveiya74codqgiixo33q62qlrqtkgmcitqx5u2oeqnmn5bpcbiyd.onion Launched May 16, 2012; 11 years ago
- anuraaga 3y agoGreat post! I respect people's decisions regarding the focus on privacy but above all I just need the internet to work and this was always a mysterious issue. Finally fixed by switching to Google DNS, which for me personally is not a problem, escaping their net is better than not but not a requirement.