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

#1

Post by ikeboy » Sat, May 04, 2019, 6:36 PM UTC

I noticed I couldn't connect to archive.is, eventually I figured out it was an issue with cloudflare DNS, 1.1.1.1. Checking nslookup confirms this:

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: 127.0.0.4

nslookup archive.is 8.8.8.8 Server: 8.8.8.8 Address: 8.8.8.8#53

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

Cloudflare is returning a localhost address which prevents you from accessing the website.

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

#2

Post by regnerba » Sat, May 04, 2019, 6:50 PM UTC

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

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

#3

Post by derimagia » Sat, May 04, 2019, 6:50 PM UTC

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

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

#4

Post by ikeboy » Sat, May 04, 2019, 6:52 PM UTC

Looks like it's a known issue https://community.cloudflare.com/t/archive-is-error-1001/182..., yet not been fixed for at least a year

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

#5

Post by systemcluster » Sat, May 04, 2019, 6:53 PM UTC

Previous discussion here: https://news.ycombinator.com/item?id=17742457

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

#6

Post by [deleted] » Sat, May 04, 2019, 6:55 PM UTC

[deleted]

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

#7

Post by floatingatoll » Sat, May 04, 2019, 6:56 PM UTC

ikeboy wrote: post #4

Looks like it's a known issue https://community.cloudflare.com/t/archive-is-error-1001/182... , yet not been fixed for at least a year

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 to contact archive.is can ask them to resolve the issue:

> If you have a contact on the domain owner, you can ask them to fix this.

EDIT: This is knowingly blocked by archive.is. Reasoning and discussion elsewhere in post comments. No need to contact archive.is about it, they’re clearly aware.

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

#8

Post by netsharc » Sat, May 04, 2019, 7:02 PM UTC

[flagged]

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

#9

Post by ikeboy » Sat, May 04, 2019, 7:03 PM UTC

floatingatoll wrote: post #7

ikeboy wrote: post #4

Looks like it's a known issue https://community.cloudflare.com/t/archive-is-error-1001/182... , yet not been fixed for at least a year

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.

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

#10

Post by darawk » Sat, May 04, 2019, 7:04 PM UTC

netsharc wrote: post #8

[flagged]

...you know that Cloudflare terminated their service, right?

https://blog.cloudflare.com/why-we-terminated-daily-stormer/