4 ms·

> I used to use 1.1.1.1 till the day I realized that it doesn't resolve archive.is. It does resolve archive.is, it’s just the archive.is nameservers return ga

> I used to use 1.1.1.1 till the day I realized that it doesn't resolve archive.is. It does resolve archive.is, it’s just the archive.is nameservers return garbage if the source if CloudFlare. CloudFlare could simply fix this their end if they wanted but haven’t done so out of integrity. This looks good for CloudFlare and bad for archive.is from where I’m sitting.

consumer451 5y ago
Is there any non-conspiratorial reason for archive.is's position on this?
- pas 5y ago
  Latency optimization. There's an argument that CF benefits if that DNS extension is not in widespread usage. (Because CF sells a CDN but if sites can "just implement" that with DNS, then there's "nothing for them to sell".)
- kerng 5y ago
  It leads to further centralization of the internet where a few have more data to make better decisions (and more money) and the smaller players are left out.
  - unityByFreedom 5y ago
    That's a fairly good argument IMO. Today's Cloudflare does not sell data. Tomorrow's, or our children's generation's, could. As you say, this could become a monopoly and it's cool to see a popular website standing up for a future where littler guys can still make it. It's not clear to me that's the precise argument he's made so I'm just guessing. When did HN get these new awesome nav buttons? Root, next, ... amazing!
- deleted 5y ago
  [deleted]
- fragmede 5y ago
  Yes. From a technical standpoint, archive.is' stance is that it's actually important useful data that, more importantly, isn't a privacy violation. How much you agree with archive.is depends on a very technical understanding of the subject, or barring that, it depends on how much you buy Cloudflare's reasoning. Cloudflare's business would prefer you pay for Cloudflare (at large but specifically their anycast) instead of using an optimization available to you as a Internet business to route clients to a more optimal/closer server. As far as the privacy implications, remember that the site you visit needs to know your IP address in order to respond to your request, so while there are some issues to be aware of, it's kind of hard to see it as a privacy violation and not Cloudflare trying to squash the little guy, imo.
  - tomklein 5y ago
    I coded a GeoDNS for a couple of my sites and Cloudflare‘s IPs are always geolocated to the nearest datacenters and works great in a GeoDNS setting. Also, what about DNS resolvers that don’t support EDNS at all?
    - tick_tock_tick 5y ago
      The check archive.is uses to return garbage is specifically for cloudflare's IPs all other non-EDNS works fine. You can dig to there authoritative DNS server yourself to see.

consumer451 5y ago

Is there any non-conspiratorial reason for archive.is's position on this?

pas 5y ago
Latency optimization. There's an argument that CF benefits if that DNS extension is not in widespread usage. (Because CF sells a CDN but if sites can "just implement" that with DNS, then there's "nothing for them to sell".)
kerng 5y ago
It leads to further centralization of the internet where a few have more data to make better decisions (and more money) and the smaller players are left out.
- unityByFreedom 5y ago
  That's a fairly good argument IMO. Today's Cloudflare does not sell data. Tomorrow's, or our children's generation's, could. As you say, this could become a monopoly and it's cool to see a popular website standing up for a future where littler guys can still make it. It's not clear to me that's the precise argument he's made so I'm just guessing. When did HN get these new awesome nav buttons? Root, next, ... amazing!
deleted 5y ago
[deleted]
fragmede 5y ago
Yes. From a technical standpoint, archive.is' stance is that it's actually important useful data that, more importantly, isn't a privacy violation. How much you agree with archive.is depends on a very technical understanding of the subject, or barring that, it depends on how much you buy Cloudflare's reasoning. Cloudflare's business would prefer you pay for Cloudflare (at large but specifically their anycast) instead of using an optimization available to you as a Internet business to route clients to a more optimal/closer server. As far as the privacy implications, remember that the site you visit needs to know your IP address in order to respond to your request, so while there are some issues to be aware of, it's kind of hard to see it as a privacy violation and not Cloudflare trying to squash the little guy, imo.
- tomklein 5y ago
  I coded a GeoDNS for a couple of my sites and Cloudflare‘s IPs are always geolocated to the nearest datacenters and works great in a GeoDNS setting. Also, what about DNS resolvers that don’t support EDNS at all?
  - tick_tock_tick 5y ago
    The check archive.is uses to return garbage is specifically for cloudflare's IPs all other non-EDNS works fine. You can dig to there authoritative DNS server yourself to see.