zlacker

[parent] [thread] 2 comments
1. 8chanA+(OP)[view] [source] 2023-08-02 18:17:16
Seems like this is no longer relevant. I just tried a DNS lookup via Cloudflare and I got 89.253.237.217.
replies(1): >>lolind+o1
2. lolind+o1[view] [source] 2023-08-02 18:23:18
>>8chanA+(OP)
I'm seeing that now too. It might have changed in the last 4 hours, or maybe the behavior is cyclical for some reason. I posted this article after running into it repeatedly over the last few weeks since switching to Cloudflare DNS.

I wonder if one party or the other actually made a change in response to this hitting the front page again?

replies(1): >>tredre+p7
◧◩
3. tredre+p7[view] [source] [discussion] 2023-08-02 18:46:46
>>lolind+o1
The behaviour is cyclical. It has been for years, really. It starts resolving every now and then, but rarely for long and I doubt this time is any different.

I don't think archive.is blocks CF based on their IPs, so they must have some heuristic in place to defect bogus EDNS. Perhaps sometimes that heuristics fails?

[go to top]