Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2026 Poal.co

484

Finally getting back to addressing this files.catbox.moe issue. My apologies for the delay in getting back to this, been busier than a one-legged man at an ass kicking contest. Not an expert on internet tech, so wasn't too excited to go on this adventure.

Anyway.. Holy shit, it looks like I fixed it; at least on my home network and on my phone. After many troubleshooting roads led me to DNS problem, I thought I'd try inputting the files.catbox.moe IP address into URL box and going there. Once I did this on both my phone and on my home network, all files.catbox.moe links work again.

Looks like for whatever reason, the DNS record for files.catbox.moe on the DNS servers I'm forced to use were non-existent, until actually going to that raw IP address forced the record to be added. But that doesn't really make sense to me... There must be thousands or hundreds-of-thousands of other users of these DNS servers I'm using, and catbox seems to get a decent amount of traffic... why would this particular record be non-existent for so long? Why just catbox?

For the small minority of others experiencing the same problem, try as I described above.

inb4 That's now how this works, that's not how any of this works, you idiot...

Edit: So this gets interesting... after about 10-15 minutes, the problem returns and I have to input IP address to get it going again... Another interesting thing to note is opening the link with Brave browser's Tor feature works all of the time.

Edit 2: Nobody is going to see this due to 2 day post age, but here we go anyway. Today, catbox working without having to do the IP instead of URL workaround. I remember reading something about that DNS records could take up to 72 hours to update. It appears that this is what happened. Been a long time since catbox has worked for me like this... But how long will this last? We'll see.

Edit 3: Discovered I can add flair... check that shit out!

Finally getting back to addressing this files.catbox.moe issue. My apologies for the delay in getting back to this, been busier than a one-legged man at an ass kicking contest. Not an expert on internet tech, so wasn't too excited to go on this adventure. Anyway.. Holy shit, it looks like I fixed it; at least on my home network and on my phone. After many troubleshooting roads led me to DNS problem, I thought I'd try inputting the files.catbox.moe IP address into URL box and going there. Once I did this on both my phone and on my home network, all files.catbox.moe links work again. Looks like for whatever reason, the DNS record for files.catbox.moe on the DNS servers I'm forced to use were non-existent, until actually going to that raw IP address forced the record to be added. But that doesn't really make sense to me... There must be thousands or hundreds-of-thousands of other users of these DNS servers I'm using, and catbox seems to get a decent amount of traffic... why would this particular record be non-existent for so long? Why just catbox? For the small minority of others experiencing the same problem, try as I described above. inb4 *That's now how this works, that's not how any of this works, you idiot...* Edit: So this gets interesting... after about 10-15 minutes, the problem returns and I have to input IP address to get it going again... Another interesting thing to note is opening the link with Brave browser's Tor feature works all of the time. Edit 2: Nobody is going to see this due to 2 day post age, but here we go anyway. Today, catbox working without having to do the IP instead of URL workaround. I remember reading something about that DNS records could take up to 72 hours to update. It appears that this is what happened. Been a long time since catbox has worked for me like this... But how long will this last? We'll see. Edit 3: Discovered I can add flair... check that shit out!

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (9).
[–] [deleted] • 1 pt

I've been through this exercise already unfortunately. What I come to find out is it doesn't matter what DNS address I put into the IPv4 properties, the ISP-provided modem/router has an unchangeable DNS server address it always uses.

There could be some underlying root cause that is no fault of the ISP, but given the symptoms they sure look like they have some degree of guilt. Right now, it looks like they have a rule in place on their DNS server to remove the record.

Rant follows.

We're back to "get your own modem and router, dipshit." I know, I know... but damnit there's a principle being broken here on the ISP side if they're truly responsible for this. Shouldn't have to be this way in the first place, they should have no business in curating content. I've got my own projects to tend to, I don't need accessing a utility to be a f-ing science project.

[–] • 1 pt

Have you tried encrypting your DNS?

https://dnscrypt.info

[–] [deleted] • 0 pt

I could give that a go just to see if it would work, but ultimately I'm going to have to install my own modem equipment. First couple of software links I clicked on both take me to git repos, that didn't seem to have any binaries included. If I have to compile the shit to use it, I'm not really inclined to put myself through potential dependency hell trying to get the shit to spit out a binary. There is a relatively simple solution, I've just been too lazy to do it.

The ISP-provided equipment I have locks me into a particular DNS, and that particular DNS doesn't seem to want to hold on to the record for catbox. Once the TTL in my local DNS cache expires, it's broken again until I visit catbox via IP address.

Have already went further down this rabbit hole this morning than I really wanted to go. Just going to have to deal with the workarounds I found until my lazy ass replaces this ISP supplied equipment.

[–] • 1 pt

What I come to find out is it doesn't matter what DNS address I put into the IPv4 properties, the ISP-provided modem/router has an unchangeable DNS server address it always uses.

If what I suggested didn't work, that was going to be my diagnosis. I had a similar problem when my ISP was trapping certain responses and fucking a lot of "We expect this result to be unresolvable" queries.

The only other thing I can suggest is if your ISP has an option to disable unresolved query ads (where they provide you a list of ads in response to a query that doesn't resolve,) turn it off. That can mess with things too.

Your ISP isn't your friend, and they data mine your traffic as much as they can.