4 ms·

Archive.is does not block all requests lacking EDNS. They specifically block requests coming from Cloudflare's datacenters. Cloudflare is not accidentally misco

Archive.is does not block all requests lacking EDNS. They specifically block requests coming from Cloudflare's datacenters. Cloudflare is not accidentally misconfiguring their EDNS, Cloudflare is intentionally not sending EDNS.

Operyl 7y ago
They’re intentionally not sending an optional extension, that seems .. fair honestly.
- cnst 7y ago
  The EDNS-Client-Subnet extension was not meant to be optional for folks running a CDN or a huge public resolver across 100+ POPs.
  - lagadu 7y ago
    "Was not meant" means nothing. It's specified as optional because it's an extension mechanism.
    - deleted 7y ago
      [deleted]
lagadu 7y ago
The "misconfiguration" he's talking about is on archive.is' part. Their configuration expects some specific server to have an optional functionality enabled, which it doesn't.
- Thorrez 7y ago
  Sorry, I don't understand. I was referring to this quote: > I think it's fair to say your site is just offline for some users due to a config mistake. Archive.is is not making an accidental mistake. Archive.is is behaving very intentionally. They've said so on Twitter. And I believe profmonocle agrees with me on that point.
  - jgrahamc 7y ago
    And Cloudflare would happily talk to archive.is to come up with a solution.
StreamBright 7y ago
And I agree with that as a Cloudflare customer. In fact if this was a paid feature I would pay for it. Just to give you more insight. Google knows which IP address I am using Gmail from. If I use 8.8.8.8 they know what other content I am looking for which websites I visit and tie that to my account. If I use something like Cloudflare who do not expose my IP (or range) then I achieved more privacy. I could use my local DNS server (like I do at home) but I travel a lot. In this case "misconfiguration" is actually for privacy and archive.is could live with that just like other sites but they intentionally screw with Cloudflare (aka the users who has 1.1.1.1 as the resolver).
dooglius 7y ago
Do you have a source for this?
- Godel_unicode 7y ago
  https://mobile.twitter.com/archiveis/status/1018691421182791680 https://mobile.twitter.com/archiveis/status/1018691421182791...
  - dooglius 7y ago
    I've seen that, it doesn't really clarify whether the block singles out cloudflare in particular, or whether cloudflare is the only (significant) DNS resolver that the block happens to affect.
- Thorrez 7y ago
  Sources for archive.is blocking Cloudflare's datacenters: The exact same command fails when sent from Cloudflare's datacenters, but succeeds when sent from DigitalOcean: https://community.cloudflare.com/t/archive-is-error-1001/18227/8 https://community.cloudflare.com/t/archive-is-error-1001/182... Two more sources: https://news.ycombinator.com/item?id=19830258 https://news.ycombinator.com/item?id=19830258 https://news.ycombinator.com/item?id=19829036 https://news.ycombinator.com/item?id=19829036

Operyl 7y ago

They’re intentionally not sending an optional extension, that seems .. fair honestly.

cnst 7y ago
The EDNS-Client-Subnet extension was not meant to be optional for folks running a CDN or a huge public resolver across 100+ POPs.
- lagadu 7y ago
  "Was not meant" means nothing. It's specified as optional because it's an extension mechanism.
  - deleted 7y ago
    [deleted]

lagadu 7y ago

The "misconfiguration" he's talking about is on archive.is' part. Their configuration expects some specific server to have an optional functionality enabled, which it doesn't.

Thorrez 7y ago
Sorry, I don't understand. I was referring to this quote: > I think it's fair to say your site is just offline for some users due to a config mistake. Archive.is is not making an accidental mistake. Archive.is is behaving very intentionally. They've said so on Twitter. And I believe profmonocle agrees with me on that point.
- jgrahamc 7y ago
  And Cloudflare would happily talk to archive.is to come up with a solution.

StreamBright 7y ago

And I agree with that as a Cloudflare customer. In fact if this was a paid feature I would pay for it. Just to give you more insight. Google knows which IP address I am using Gmail from. If I use 8.8.8.8 they know what other content I am looking for which websites I visit and tie that to my account. If I use something like Cloudflare who do not expose my IP (or range) then I achieved more privacy. I could use my local DNS server (like I do at home) but I travel a lot. In this case "misconfiguration" is actually for privacy and archive.is could live with that just like other sites but they intentionally screw with Cloudflare (aka the users who has 1.1.1.1 as the resolver).

dooglius 7y ago

Do you have a source for this?

Godel_unicode 7y ago
https://mobile.twitter.com/archiveis/status/1018691421182791680 https://mobile.twitter.com/archiveis/status/1018691421182791...
- dooglius 7y ago
  I've seen that, it doesn't really clarify whether the block singles out cloudflare in particular, or whether cloudflare is the only (significant) DNS resolver that the block happens to affect.
Thorrez 7y ago
Sources for archive.is blocking Cloudflare's datacenters: The exact same command fails when sent from Cloudflare's datacenters, but succeeds when sent from DigitalOcean: https://community.cloudflare.com/t/archive-is-error-1001/18227/8 https://community.cloudflare.com/t/archive-is-error-1001/182... Two more sources: https://news.ycombinator.com/item?id=19830258 https://news.ycombinator.com/item?id=19830258 https://news.ycombinator.com/item?id=19829036 https://news.ycombinator.com/item?id=19829036