Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 210 posts

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#11

Post by akerro »

regnerba wrote: post #2

Cloudflare returns a proper response for me. 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: 134.119.220.26

    dig @1.1.1.1 archive.is
    
    ; > DiG 9.14.1 > @1.1.1.1 archive.is
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER> DiG 9.14.1 > @8.8.8.8 archive.is
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#12

Post by 1f60c »

regnerba wrote: post #2

Cloudflare returns a proper response for me. 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: 134.119.220.26

Not for me:

    Server:  1.1.1.1
    Address: 1.1.1.1#53

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

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#13

Post by akerl_ »

ikeboy wrote: post #9
floatingatoll wrote: post #7

Earlier quoted context omitted.

In response to that "unfixed" issue, they noted - in a timely manner, last year - that archive.is is returning bad IPs to them, which is preventing them from serving good IPs: https://community.cloudflare.com/t/archive-is-error-1001/182... > Nameservers responsible for archive.is (ben.archive.is, anna.archive.is) are returning answers tailored to the IP address of the requestor. And indicate that anyone who knows how…

Just like we consider it the kernel's fault if user applications break due to a change, I think it's the DNS resolver's fault if they're using a protocol that some popular sites don't support. As soon as I realized they were causing this issue I just switched away. Other DNS providers don't have this issue.

It doesn’t really seem to be the resolvers “using a protocol that [archive.is] doesn’t support”; it seems that archive.is responds to queries from Cloudflare’s systems with an incorrect response. How is Cloudflare meant to work around that kind of behavior?

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#14

Post by irtefa »

This has been a known issue for a while.

Unfortunately, Archive.is has to fix it from their nameservers and we cannot do anything from our side. You can ready more about it here: https://community.cloudflare.com/t/archive-is-error-1001/182...

Disclaimer: I work at Cloudflare

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#15

Post by fmhul »

darawk wrote: post #10
netsharc wrote: post #8

[flagged]

...you know that Cloudflare terminated their service, right? https://blog.cloudflare.com/why-we-terminated-daily-stormer/

And even if they hadn't, how would that make them "Nazi-friendly"? I've always supposed Cloudflare is meant to be neutral. They only kicked out DS because they were stupid enough to pretend CF was endorsing them.

And well, in any case this is unrelated to this thread...

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#18

Post by judge2020 »

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.

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#20

Post by ignoranceprior »

derimagia wrote: post #3

I remember reading this a while back. It sounded more that archive.is was blocking Cloudflare (or at least not supporting it): https://community.cloudflare.com/t/archive-is-error-1001/182...

Does anyone know why archive.is would block Cloudflare? Is it a technical issue, or does the owner of archive.is have some kind of grudge against them?
Post reply on HN