Comment by judge2020

7 years ago

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.

20 comments

judge2020

Reply
Chlorus  7 years ago

I take back every bad thing I have ever said about mailing lists - at least it was easier to follow the drama than these damn twitter links.

  • maccard  7 years ago

    My issue with mailing lists is the browsing experience. It's very difficult to view conversations, especially compared to Gmail's threaded view. Seems like something an open source project could solve!

floatingatoll  7 years ago

Text of tweet by @archiveis:

"Having to do" is not so direct here. Absence of EDNS and massive mismatch (not only on AS/Country, but even on the continent level) of where DNS and related HTTP requests come from causes so many troubles so I consider EDNS-less requests from Cloudflare as invalid.

  • arghwhat  7 years ago

    For additional context, here is the Cloudflare explanation about EDNS client subnets:

    > 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.

    Cloudflare's requests are of course perfectly valid, with @archiveis actively deciding not to service them.

    • zzzcpan  7 years ago

      It has nothing to do with privacy, as the next thing following DNS resolution is establishing a TCP connection which always leaks full IP address to the same person or organization controlling authoritative servers. Basically EDNS is just a convenient way for DNS-based CDNs to provide a better edge node. But this is directly competing with Cloudflare, so Cloudflare invents excuses not to implement something that helps other CDNs.

      11 replies →

  • viraptor  7 years ago

    > requests come from causes so many troubles

    Given they serve their pages over tor, I don't buy that explanation at all. Assuming location of client == location of CloudFlare source would give them a rough match in most cases. In tor they're almost guaranteed to be wrong.

  • Aeolun  7 years ago

    Ah yes, the huge trouble of a website that is a few MS slower as opposed to just not working at all.

    I’m not sure I see what kind of logic goes into this argument.