Feedback Technical Grievances

  • Welcome to the last real website on the Internet. Join today, if you dare.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Image uploads are completely fucked over tor - but that's just a background issue.
Adult_Child_1.jpg
works fine 4 me - tor browser on linux
Attach files has always been broken in tor browser (something about canvas), you have to do it via insert image
 
It's looking like empty/NODATA DNS records have been propagated globally for .net and .cc (:_(

1783897252548.png
All except DigitalOcean's resolvers which are returning 0.0.0.0 just for .net. Guessing they just had it blocked already for some reason and it's still returning that useless value instead of NODATA.


Could be 4D chess by Null if he's just wanting to give the ddos nothing to point at for a while.
 
How the hell did the site get blasted out of DNS? Was that the attacker or Jersh? If it was Jersh, I wouldn’t expect him to enumerate his defensive tactics, but call me professionally curious.

Could be 4D chess by Null if he's just wanting to give the ddos nothing to point at for a while.
Possibly, but I’ve never seen a sane operator do that, it’s too easy to shitcan other stuff. Better to just set your firewall to blacklist everything if you are going into desperate defense mode. Usually if null records get propagated/cached it’s a fuckup.
 
Last edited:
Apple music does not embed the playlist properly. When inserting a song or artist, it does not want to embed and must be manually typed out.
Following up with Apple Music, it appears that the content is blocked.
Screenshot_20260713_035307_Chrome.png
Is this an issue that could be fixed? I didn't know websites could block specific sites from sharing their content.
 
How the hell did the site get blasted out of DNS? Was that the attacker or Jersh? If it was Jersh, I wouldn’t expect him to enumerate his defensive tactics, but call me professionally curious.
Speculation: the A record is populated from a list of "healthy" Tartarus front-ends, and they all went unhealthy at the same time.

Usually if null records get propagated/cached it’s a fuckup.
Similar systems on which I've worked in the past had fallback logic for the "none healthy" case (e.g. "pick an unhealthy node at random"), for this reason.
 
Still having issues with DNS.

> set q=A
> server ult01.dnspod.com
Default server: ult01.dnspod.com
Address: 43.134.249.72#53
Default server: ult01.dnspod.com
Address: 117.135.128.172#53
Default server: ult01.dnspod.com
Address: 163.177.5.76#53
Default server: ult01.dnspod.com
Address: 1.12.0.64#53
Default server: ult01.dnspod.com
Address: 1.12.0.65#53
Default server: ult01.dnspod.com
Address: 1.12.0.66#53
Default server: ult01.dnspod.com
Address: 1.12.14.64#53
Default server: ult01.dnspod.com
Address: 1.12.14.65#53
Default server: ult01.dnspod.com
Address: 1.12.14.66#53
Default server: ult01.dnspod.com
Address: 43.130.172.72#53
> kiwifarms.st
Server: ult01.dnspod.com
Address: 43.134.249.72#53

*** Can't find kiwifarms.st: No answer
> server ult02.dnspod.com
Default server: ult02.dnspod.com
Address: 1.12.14.68#53
Default server: ult02.dnspod.com
Address: 1.12.14.69#53
Default server: ult02.dnspod.com
Address: 43.140.57.73#53
Default server: ult02.dnspod.com
Address: 43.161.3.72#53
Default server: ult02.dnspod.com
Address: 170.106.122.172#53
Default server: ult02.dnspod.com
Address: 220.196.136.72#53
Default server: ult02.dnspod.com
Address: 1.12.0.67#53
Default server: ult02.dnspod.com
Address: 1.12.0.68#53
Default server: ult02.dnspod.com
Address: 1.12.0.69#53
Default server: ult02.dnspod.com
Address: 1.12.14.67#53
> kiwifarms.st
Server: ult02.dnspod.com
Address: 1.12.14.68#53

*** Can't find kiwifarms.st: No answer
 
I wonder how expensive this sort of attack is. I know Null has alluded to it in vague terms but surely their purse has limits.
 
Back
Top Bottom