Hacker News Reader

Comment by 7sovaren | Hacker News Reader

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

View on HN

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

Im using iCloud Private Relay, and it affects me.

I’m using iCloud Private Relay and it works fine.

I use iCloud Private Relay and it only affects me over IPv6. Disabling either private relay or ipv6 "fixes" it

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

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

> Nobody cares; the reality is if you use CF DNS, shit don't work.

This is super misleading because it ignores the fact that archive.* goes out of their way to make CF DNS not work.

Doesn't really change anything for the end-user that wants to access the website and is bummed that it doesn't work. There might be politics in the way but all they care is that it doesn't work.

> goes out of their way to make CF DNS not work.

No, they go out of their way to make a system that can handle people trying to abuse it. Cloudflare doesn't like that system and refuses to help them.

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

Isn't the Internet full of major websites that need to be able to handle that kind of abuse? If what archive.* did were really necessary to do so, then why haven't any other websites needed to do the same thing?

>Isn't the Internet full of major websites that need to be able to handle that kind of abuse?

I don't know; since their whole reason for being is to act as (a temporary?) archive of websites that would make them more vulnerable to these attacks than someone like ebay I'd think?

But archive.org provides the same service as them, and it doesn't need to do that.

It’s not the same service, though.

As I understand it, the main reasons people use archive.is over archive.org are because archive.is is more of an immediate proxy/cache/cdn, rather than a long-term archival system that requires a bot to crawl based on schedule parameters. That, and also it includes features to help bypass paywalls by sanitizing some (all?) JavaScript.

On the other hand, Archive.org doesn’t remove or alter scripts or anything like that. And as far as I know you can’t just request them to crawl a site and then browse it there immediately, but you can on Archive.is

> And as far as I know you can’t just request them to crawl a site and then browse it there immediately, but you can on Archive.is

Yes you can. After you put in the URL, you get a button to do so. I just did it for your comment: https://web.archive.org/web/20230802205505/https://news.ycom...

> Supposedly Cloudflare uses a feature of DNS archive.* doesn't like, or vice versa.

From what I understand, it's the opposite: Cloudflare doesn't use a relatively new feature of DNS (EDNS Client Subnet), and that site doesn't like the lack of that feature.

I get the same result when I query 1.1.1.1 or 1.0.0.1 for archive.is:

    ┌
    └─(12:32:59)──> nslookup archive.is 1.1.1.1 
                                            
    Server:  1.1.1.1
    Address: 1.1.1.1#53

    Non-authoritative answer:
    Name: archive.is
    Address: 89.253.237.217

    ┌
    └─(12:38:12)──> nslookup archive.is 1.0.0.1
                                            
    Server:  1.0.0.1
    Address: 1.0.0.1#53

    Non-authoritative answer:
    Name: archive.is
    Address: 89.253.237.217

Wonder why that is happening...

Reply on news.ycombinator.com