Author

Topic: archive.today / archive.fo / archive.??? being blocked by some ISPs (DNS ISSUE) (Read 171 times)

legendary
Activity: 2870
Merit: 7490
Crypto Swap Exchange
At least if you use 1.1.1.1 as DNS, this issue is already few known for past few years. According at https://webapps.stackexchange.com/q/135222, the problem is complicated and looks like won't be solved anytime soon. I would recommend people to use different archive service if they wish everyone could see archived page easily.

Thanks for finding that.
I am surprised that archive.today does not have that piece of information on their front page.

Such information doesn't fit front page, unless it recently happened. Seperate page to mention technical problem would be better.

And you can get to archive.today with the other provider that they include nextdns. But, I do not know a thing about them.

NextDNS have better privacy policy than Cloudflare, people should choose it (or input different DNS link) if they care about privacy.
legendary
Activity: 3458
Merit: 6231
Crypto Swap Exchange
At least if you use 1.1.1.1 as DNS, this issue is already few known for past few years. According at https://webapps.stackexchange.com/q/135222, the problem is complicated and looks like won't be solved anytime soon. I would recommend people to use different archive service if they wish everyone could see archived page easily.

Thanks for finding that.
I am surprised that archive.today does not have that piece of information on their front page.

Such information doesn't fit front page, unless it recently happened. Seperate page to mention technical problem would be better.

But there is not any link on their site that I can see that says "having issues reaching us at times, click here"
Even you posted the link from slackexchnage about it, nothing on their archive itself.
Yes, I am complaining about a customer service issue on a free site / service. But, how many people try it, have it not work for one reason or another and never go back to them.

Now, with firefox pushing the secure DNS and using cloudflare by default I don't see the situation getting better.

-Dave
legendary
Activity: 3458
Merit: 6231
Crypto Swap Exchange
At least if you use 1.1.1.1 as DNS, this issue is already few known for past few years. According at https://webapps.stackexchange.com/q/135222, the problem is complicated and looks like won't be solved anytime soon. I would recommend people to use different archive service if they wish everyone could see archived page easily.

Thanks for finding that.
I am surprised that archive.today does not have that piece of information on their front page.

Keep in mind that by default if you use firefox and choose the secure DNS option that they want you to it uses the Cloudflare DNS servers.
So there are probably a lot of people who use firefox choose the secure DNS option and now can't get to them.

You can change the settings in Firefox here:
https://support.mozilla.org/en-US/kb/firefox-dns-over-https#w_manually-enabling-and-disabling-dns-over-https

And you can get to archive.today with the other provider that they include nextdns. But, I do not know a thing about them.

-Dave
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
I would recommend people to use different archive service if they wish everyone could see archived page easily.
I tried to make my own, but that was HTML only. If there's an open source archiving software available, I wouldn't mind setting up my own service for Bitcointalk only.
legendary
Activity: 2870
Merit: 7490
Crypto Swap Exchange
At least if you use 1.1.1.1 as DNS, this issue is already few known for past few years. According at https://webapps.stackexchange.com/q/135222, the problem is complicated and looks like won't be solved anytime soon. I would recommend people to use different archive service if they wish everyone could see archived page easily.
legendary
Activity: 3668
Merit: 2218
💲🏎️💨🚓
I'm in Australia and I type archive.today into my browser and it is redirected to archive.ph (and has been for about two years now)

Before that archive.today would send a user to their least mirrored site (by activity) so you could end up at different (dot) extensions each day.

If I try to use Tor Browser, archive.today (etc) will have various warnings and captchas (most of which fail)

archive.today etc had a DDOS attack about three years ago which prompted the above measures.
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!
In my case .today redirects to archive.ph (although I'm not from the Philippines)
Usually I just use archive.is and I'm fine; and it works now too.

Maybe arhive.today is some load balancer/redirector and one of the targets is down?
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
Looks like it's the dot today domain on my end that's the problem.

When I do it with one network, putting in the dot today redirects to dot ph and loads fine. On a different (still secure) network I get "connection interrupted" when trying to dot today domain but not with the dot ph... I'd recommend reporting it to the dns provider and the service (the archive service ought be able to fix it faster).
legendary
Activity: 3458
Merit: 6231
Crypto Swap Exchange
Accessing the .fo is fine to me, but when accessing the .today domain redirects me to the .md domain.

It does not do that for one public DNS that I checked but, it does redirect to .vn on another public DNS.
I wonder if archive is doing something odd for redirection that is causing an issue on some DNS servers.
Or is it just a rotational redirect and one of them is broken and the cable DNS are waiting for the TTL to time out before going to the next.

Will have to check if I get back to the office later and can do more testing.

For now I changed the subject to reflect that.

-Dave
copper member
Activity: 2142
Merit: 1305
Limited in number. Limitless in potential.
Accessing the .fo is fine to me, but when accessing the .today domain redirects me to the .md domain.
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
As you already mentioned, this is a DNS issue. These sites are working on my ISP's DNS. Maybe you should call Spectrum and tell them about the problem? I can't imagine they would intentionally block these websites, based on the fact that they mainly serve the USA.
legendary
Activity: 3458
Merit: 6231
Crypto Swap Exchange
Since a lot of people like to use it for archiving posts for reputation.
I had this in meta and some mod moved it, to off-topic. I think it's better here.
Just my opinion.

It's not much of a block but while browsing Ratimovs post https://bitcointalksearch.org/topic/m.57979125 when clicking on the links it took me nowhere.

Thought it was odd and did some more checking. Turns out some ISPs or at least optimum are either deliberately blocking the site or have their DNS servers so screwed up you can't get to it.

Using 8.8.8.8 or 1.1.1.1 or 9.9.9.9 will get you to the site.

Using a PC I have access to on Fios it works.
Usain a PC I have access to on Spectrum it does not.

I don't know if this is a transient issue, or if it's deliberate, or even if Optimum / Spectrum even run their own DNS or subcontract it out so it might not even be them.

Just an FYI to people, who use the archive.*** service it may not work for some people.

It was working sometime last week, don't remember when I last clicked on one of those links.

-Dave

From cable:
Code:
HEADER:
    opcode = QUERY, id = 29796, rcode = NOERROR
    header flags: reply, want recursion, recursion avail.
    questions = 1, answers = 1, auth. records = 0, additional = 0
QUESTIONS:
    archive.today., type = XX, class = 1
ANSWERS:
->  archive.today.
    type = CNAME, class = 1, ttl = 60, dlen = 19
    alias = www.archive.today.

So I look up www.archive.today and get:

HEADER:
    opcode = QUERY, id = 29841, rcode = NOERROR
    header flags: reply, want recursion, recursion avail.
    questions = 1, answers = 0, auth. records = 0, additional = 0
QUESTIONS:
    www.archive.today., type = XX, class = 1

**complete**


Using 8.8.8.8 it works properly:

Code:
HEADER:
    opcode = QUERY, id = 29891, rcode = NOERROR
    header flags: reply, want recursion, recursion avail.
    questions = 1, answers = 1, auth. records = 0, additional = 0
QUESTIONS:
    archive.today., type = XX, class = 1
ANSWERS:
->  archive.today.
    type = A, class = 1, ttl = 300, dlen = 4
    IP address = 151.106.9.30

**complete**

Jump to: