Archive.fo sinkholed by CloudFlare? - What the fuck DNS do I use now?

Wingus Dongshire

kiwifarms.net
Joined
Dec 22, 2018
Sorry if this is a repeat, I tried searching but "archive.fo" isn't exactly a unique string on the farms and the "search title only" button seems to do nothing.

I was digging through some threads on my weekly "I'm bored as fuck, time to lurk" period and noticed I got 404'd for archive.fo ridiculously quickly. Naturally, I wondered if either my pi-hole was blocking it (like it did the farms) or if my upstream DNS provider is sinkholing it.

So, having a closed AirVPN account and being too strapped to renew just to test this, I decided to poke around resolving it through my standard upstream (CloudFlare)

720853


Finding it strange that I was getting a loopback reserved IP from it, I decided to check the nameservers and lo and behold, CloudFlare is the nameserver.

Likewise, here's Google's results:

720855


However, that IP just returns the out-of-the-box NGINX landing page
720857


Furthermore, the SSL cert bound to that page is for "adieo.com"
720858


Archive.is resolves normally (which is weird, since that's the one they stated would be getting shut down) but doesn't actually respond to my HTTP/S traffic.

Judging from the fact that archive.fo resolves from (seemingly) the proper nameservers but I get this, I'm unsure if it's been hijacked/shutdown or if it's being actively censored.

If the former, why the NS fuckwittery from CloudFlare?
If the latter, the fuck DNS do I use now?
 
I just put tried archive.fo, using firefox, and airvpn. and it came up OK.
 
This has been going on for a long time. I discovered this a few months ago when I kept having problems resolving archive.is/.fo/etc with 1.1.1.1. I searched around and found it talked about on Cloudflare forum. Cloudflare blames archive.is: https://community.cloudflare.com/t/1-1-1-1-does-not-resolve-archive-is/28059

Archive.is has chosen not to publish their IP addresses to Cloudflare DNS resolvers. You’ll need to take up the issue with them.

Archive.is blames Cloudflare: https://twitter.com/Taubin/status/1081696635640373248

Thus, I went back to 8.8.8.8.

Edit - For some reason archive . is is auto correcting to archive.li? But not like a normal wordfilter. I see .is when I edit, but when I save, it's shows .li @Null
 
Last edited:
I just put tried archive.fo, using firefox, and airvpn. and it came up OK.
Are you network locked? Does it work without AirVPN? Because I'm currently too poor to renew my sub until Friday and it's getting in the way of my auts.

Also just checked to make sure, my internal DNS isn't blocking it
720888


This has been going on for a long time. I discovered this a few months ago when I kept having problems resolving archive.li/.fo/etc with 1.1.1.1. I searched around and found it talked about on Cloudflare forum. Cloudflare blames archive.li: https://community.cloudflare.com/t/1-1-1-1-does-not-resolve-archive-is/28059



archive.li blames Cloudflare: https://twitter.com/Taubin/status/1081696635640373248

Since only Cloudflare seems to have this issue, I'm going to blame Cloudflare.

Thus, I went back to 8.8.8.8.

Edit - For some reason archive . is is auto correcting to archive.li? But not like a normal wordfilter. I see .is when I edit, but when I save, it's shows .li @Null
Still getting a 404 on 8.8.8.8, sadly. Even bypassed my internal DNS. Guess I'll just have to deal 'til I get my VPN back up. Still dunno what the fuck that "adieo.com" thing was about, unless they have FQDN NATting for HTTP requests on some shared hosting server, which I can't imagine they would given their storage-heavy nature.
 
Last edited:
Are you network locked? Does it work without AirVPN? Because I'm currently too poor to renew my sub until Friday and it's getting in the way of my auts.

Also just checked to make sure, my internal DNS isn't blocking it
View attachment 720888

Still getting a 404 on 8.8.8.8, sadly. Even bypassed my internal DNS. Guess I'll just have to deal 'til I get my VPN back up. Still dunno what the fuck that "adieo.com" thing was about, unless they have FQDN NATting for HTTP requests on some shared hosting server, which I can't imagine they would given their storage-heavy nature.
I have not tried it without a vpn....I only go online using a vpn. I'm trying to think of a free vpn...I think that there is proton, also windscribe and also riseup use bitmask - but I think you might need to use linux to use that. the other cheap and kind of nasty almost a vpn is built into opera.....it does get around a lot of dns blocks and so on.
Network locked? Not sure what you mean.
 
This is getting fucking weirder, now on 8.8.8.8 manually hitting the IP fails on HTTPS but pulls up a fedora nginx landing page on HTTP, markedly different from the vanilla nginx page.

720904


Can someone look up the PTR record for 51.83.68.44 and confirm it is officially 44.ip-51-83-68.eu? I'm starting to wonder if I'm getting MITMed or my ISP is being an asshole.

I have not tried it without a vpn....I only go online using a vpn. I'm trying to think of a free vpn...I think that there is proton, also windscribe and also riseup use bitmask - but I think you might need to use linux to use that. the other cheap and kind of nasty almost a vpn is built into opera.....it does get around a lot of dns blocks and so on.
Network locked? Not sure what you mean.
Network Lock is the privacy enforcement for AirVPN that disables your NIC if it loses its tunnel.

It's working on cellular network, so I'm gonna chalk this up to "ISP garbage" since any DNS-based traffic to that name just sends TCP synchronize retransmissions out to the void without any response.

AND AS SOON AS I SAY THAT IT STARTS WORKING AGAIN.
Fuck the world wide web, I'm going back to usenet.
 
Last edited:
This is getting fucking weirder, now on 8.8.8.8 manually hitting the IP fails on HTTPS but pulls up a fedora nginx landing page on HTTP, markedly different from the vanilla nginx page.

View attachment 720904

Can someone look up the PTR record for 51.83.68.44 and confirm it is officially 44.ip-51-83-68.eu? I'm starting to wonder if I'm getting MITMed or my ISP is being an asshole.


Network Lock is the privacy enforcement for AirVPN that disables your NIC if it loses its tunnel.

It's working on cellular network, so I'm gonna chalk this up to "ISP garbage" since any DNS-based traffic to that name just sends TCP synchronize retransmissions out to the void without any response.

AND AS SOON AS I SAY THAT IT STARTS WORKING AGAIN.
Fuck the world wide web, I'm going back to usenet.
Ah. Right. It's on my eddie front page and its enabled. must one day learn to connect the dots...
Is this what you are after:
723220
 
archive.is/.fo/.today seems to be not responding anymore when using CloudFlare's 4dot1 (1.1.1.1) DNS anymore? [ERR_CONNECTION_TIMED_OUT]
Edit: It's random as fuck, not using VPN and for me it's just either loading the site after a very long time or shitting out. Dunno, worked fine for several days now.

Obviously, am switching DNS and flushing the cache or testing on different VPS's. Might just be a temp thing but it's being strange, again.
 
I just logged on to archive.fo. It seems OK.
Huh, can't seem to wrap my head around it then. Only thing I can come up with is some fucked by-country kind of situation since everything I'm using is within the same country.
Even then, why would they start to do that?
 
I use DNSCrypt through my VPN and I can't connect to archive.li or .fo anymore either. I'm getting the feeling this is on their end, because this is recent. I can't see DNSCrypt actively blocking archive .
 
It's happening, again. I'm seeing the redirect to Nginx somebody mentioned a few years, ago. I was able to get past that, for a while, by using an IP anonymizing proxy to connect to archive.is, but now I'm starting to get this error message.

"
/**/

Not Found (yet?)​

/**/
"

I see it especially often when trying to archive tweets, for some reason. At least a few different people reported the problem to the owner, who couldn't be bothered to reply. Finding out that this is, in fact, an ancient issue was helpful, if not very encouraging. Obviously, if the problem is still here three years later, the guy isn't going to come around. We just need to find a new archiving service. Or maybe a new hobby.

The new hobby sounds like a better choice.
 
Back