4 ms·

Link is dead

meibo 6y ago
You can't open archive.is links with Cloudflare DNS since the owner of the service thinks that they are ruining the internet.
- eurg 6y ago
  Thanks for the explanation. I don't really understand why this service owner wants me rather using my censored ISP provided DNS, or Google's, but I'm sure they have a good reason.
  - Nullabillity 6y ago
    It's not so much those two in particular, as it is anything but Cloudflare (for reasons I've already gone through elsewhere[0][1]). Running your own resolver would also work fine. [0]: https://news.ycombinator.com/item?id=25973190 https://news.ycombinator.com/item?id=25973190 [1]: https://news.ycombinator.com/item?id=25973145 https://news.ycombinator.com/item?id=25973145
- 6gvONxR4sf7o 6y ago
  Cloudflare is doing this to archive or archive is doing this to cloudflare users?
  - Nullabillity 6y ago
    They're doing it to each other. Cloudflare is pretty much the only DNS resolver that doesn't provide the source user's IP address when doing recursive requests. Archive.is is pretty much the only (big) website that refuses to answer DNS requests at all if they don't include the source IP address. Cloudflare argues that this improves privacy (nevermind that the user's IP shows up anyway as soon as they try to actually connect). Archive.is argues that this prevents them from doing geographic load balancing (which, as it turns out, just happens to be a separate product that Cloudflare is happy to sell to websites).
- CharlesW 6y ago
  > You can't open archive.is links with Cloudflare DNS since the owner of the service thinks that they are ruining the internet. archive.is blames Cloudflare, but in reality it's easy to verify that archive.is's nameservers are returning different IP addresses depending on the network you're coming in from. This is clearly broken on their end. Cloudflare literally can't fix this. archive.is is 100% responsible.
  - Nullabillity 6y ago
    > but in reality it's easy to verify that archive.is's nameservers are returning different IP addresses depending on the network you're coming in from. Yes, this is the whole point of (this part of) EDNS. It allows you to direct the traffic to a server close to the end user (geographically or based on peering preferences). > This is clearly broken on their end. There are two broken things here: 1. Cloudflare doesn't send the source IP with the DNS request 2. Archive.is would rather not respond to broken requests at all than make a best-effort with a degraded experience Considering that Cloudflare is pretty much the only public DNS server with this problem, and the only motivation seems to be that it competes with their CDN product, I'm far more sympathetic to Archive.is than to Cloudflare. > Cloudflare literally can't fix this. archive.is is 100% responsible. Only Cloudflare can fix this properly. Archive.is can work around it (at the cost of degraded performance), but I can understand why they would want to stand their ground.
    - CharlesW 6y ago
      > Cloudflare doesn't send the source IP with the DNS request Yes, because (as they've stated elsewhere) EDNS subnet information leaks information about a requester's IP. > Archive.is would rather not respond to broken requests at all than make a best-effort with a degraded experience Broken responses = the most degraded experience. Is there any other website that just fails when they aren't handed EDNS subnet information? I've never experienced any.
      - Nullabillity 6y ago
        > Yes, because (as they've stated elsewhere) EDNS subnet information leaks information about a requester's IP. The requester's IP leaks anyway as soon as they actually try to connect.
deleted 6y ago
[deleted]

Link is dead

You can't open archive.is links with Cloudflare DNS since the owner of the service thinks that they are ruining the internet.

eurg 6y ago
Thanks for the explanation. I don't really understand why this service owner wants me rather using my censored ISP provided DNS, or Google's, but I'm sure they have a good reason.
- Nullabillity 6y ago
  It's not so much those two in particular, as it is anything but Cloudflare (for reasons I've already gone through elsewhere[0][1]). Running your own resolver would also work fine. [0]: https://news.ycombinator.com/item?id=25973190 https://news.ycombinator.com/item?id=25973190 [1]: https://news.ycombinator.com/item?id=25973145 https://news.ycombinator.com/item?id=25973145
6gvONxR4sf7o 6y ago
Cloudflare is doing this to archive or archive is doing this to cloudflare users?
- Nullabillity 6y ago
  They're doing it to each other. Cloudflare is pretty much the only DNS resolver that doesn't provide the source user's IP address when doing recursive requests. Archive.is is pretty much the only (big) website that refuses to answer DNS requests at all if they don't include the source IP address. Cloudflare argues that this improves privacy (nevermind that the user's IP shows up anyway as soon as they try to actually connect). Archive.is argues that this prevents them from doing geographic load balancing (which, as it turns out, just happens to be a separate product that Cloudflare is happy to sell to websites).
CharlesW 6y ago
> You can't open archive.is links with Cloudflare DNS since the owner of the service thinks that they are ruining the internet. archive.is blames Cloudflare, but in reality it's easy to verify that archive.is's nameservers are returning different IP addresses depending on the network you're coming in from. This is clearly broken on their end. Cloudflare literally can't fix this. archive.is is 100% responsible.
- Nullabillity 6y ago
  > but in reality it's easy to verify that archive.is's nameservers are returning different IP addresses depending on the network you're coming in from. Yes, this is the whole point of (this part of) EDNS. It allows you to direct the traffic to a server close to the end user (geographically or based on peering preferences). > This is clearly broken on their end. There are two broken things here: 1. Cloudflare doesn't send the source IP with the DNS request 2. Archive.is would rather not respond to broken requests at all than make a best-effort with a degraded experience Considering that Cloudflare is pretty much the only public DNS server with this problem, and the only motivation seems to be that it competes with their CDN product, I'm far more sympathetic to Archive.is than to Cloudflare. > Cloudflare literally can't fix this. archive.is is 100% responsible. Only Cloudflare can fix this properly. Archive.is can work around it (at the cost of degraded performance), but I can understand why they would want to stand their ground.
  - CharlesW 6y ago
    > Cloudflare doesn't send the source IP with the DNS request Yes, because (as they've stated elsewhere) EDNS subnet information leaks information about a requester's IP. > Archive.is would rather not respond to broken requests at all than make a best-effort with a degraded experience Broken responses = the most degraded experience. Is there any other website that just fails when they aren't handed EDNS subnet information? I've never experienced any.
    - Nullabillity 6y ago
      > Yes, because (as they've stated elsewhere) EDNS subnet information leaks information about a requester's IP. The requester's IP leaks anyway as soon as they actually try to connect.

deleted 6y ago

[deleted]