Torrentleech Hit And Run

[Kayleen]

wheni download from torrentleech the down speed is between 500-1000 kb/s but the seeding is only 1-10 kb/s, but if i download from piratebay the seeding is 60-90 kb/s. i have tried port forwading and turning of all firewalls but witout succes.

If you're firewalled, the uploading and downloading results can be very reduced. But it all depends on how many others (percent-wise!) are also firewalls. If everyone was firewalled, NOTHING could be downloaded and uploaded! Even most of the NAT Transversal tricks won't work in a totally firewalled environment.

So on 1 tracker, there's more firewalled people than others...and as a result even SEEDING is slower while you yourself are firewalled. Generally, being firewalled also means less likely to be using reasonable limits -- so even more people will get crappy download and upload speeds as a result.

Some of the private trackers and even a couple public trackers are so seed-heavy that once you become a seed you will actually have trouble finding a peer to upload to. And even if you do connect to a peer, it's likely one that's already maxed-out so you cannot upload to them quickly. The really slow peers would be around longer and make you more likely to connect to them than a short-lived fast peer.

I am very wary of D-Link routers, due to the huge number of reports of problems. They can't use UPnP or DMZ without extreme problems. Even DHT in Torrent can cause issues on some of them. Wireless no doubt makes all that worse, as any background radio waves can cause interferance and slowdowns/disconnections. So with wireless you have to reduce the Global connections and connections per torrent at least. Half-open connection max in Torrent needs to be left the default of 8, just to be on the safe side.

Cannot reproduce on Kitalpha, CH.

Still, there seems to be a problem with that domain's DNS config: The NIC of .org lists dns101 and dns102 as the two authoritative nameservers for torrentleech.org (they're the parent). The local zone file of torrentleech.org on the other hand lists two additional NS records, dns1 and dns2; I believe they're a remnant of a recently done name change which whoever runs torrentleech.org didn't reflect yet. It's a local-parent mismatch and can render the site unreachable if a resolver prefers to use the local zone information from torrentleech.org (though, I don't know if that is a setting one can influence). Some of these nameservers can potentially send records for torrentleech.org with obsolete information, and I suspect this is what's happening here: dns101 and dns102 hold the true up-to-date info, but your resolver decided to use the local info dns1 or dns2 sent, which potentially contain a wrong A/AAAA record for torrentleech.org or, as it seems to be in this case, no info on torrentleech.org at all.

We can check on that by looking at which nameserver your resolver gets its info from. If you are connected and you see that torrentleech.org is "unreachable", assuming you are on Windows because of the mouse model in the screenshot, try this in a command prompt/PowerShell and post the results:

3a8082e126