undefined | Better HN

0 pointsksec3y ago0 comments

I dont know but transmission 3.0 era uses 200K+ DNS lookup with about 30 active torrent in a space of two to three weeks. I dont think I ever got to the bottom of it.

0 comments

archi423y ago

200k queries in two weeks? That's not a lot. For waking hours and with someone surfing the web, my pihole reports about 1000/10m. That's 1.6/s.

Also, why would you have a DNS quota? I guess some DNS blocker service like NextDNS? Either pay them the money, put a local cache on your torrent client (or use a pihole with blocklists), or have the machine with the torrent client use another DNS server.

londons_explore3y ago

Thats like 1 per second. Which isn't really much. Thats probably 1 per person who connects or tries to connect to your machine.

oefrha3y ago

A BT client doesn’t need to do DNS resolution for peers, since peers are bare IP addresses. It does need to resolve DNS for tracker domains when periodically announcing, and a public torrent can have a lot of trackers. Those add up if tracker domains have low TTL, I suppose.

londons_explore3y ago

Most BT clients do do a lookup of IP addresses. Many do it to provide little flags in the UI to say which country a user is from. Some also use the results as part of an algorithm to ban bad clients (if all clients from the same ISP are sending bad data, ban the whole ISP).

1 more reply

j / k navigate · click thread line to collapse

0 comments

archi423y ago

200k queries in two weeks? That's not a lot. For waking hours and with someone surfing the web, my pihole reports about 1000/10m. That's 1.6/s.

londons_explore3y ago

Thats like 1 per second. Which isn't really much. Thats probably 1 per person who connects or tries to connect to your machine.

oefrha3y ago

londons_explore3y ago

1 more reply

j / k navigate · click thread line to collapse