mucklark

Well, trackers give out the addresses of peers. If those addresses were given out as hostnames, there'd be a lot of DNS work involved, but they don't (as far as I'm aware).

So then the DNS curb would be looking up the hostnames of the trackers, which I'd guess would be under a dozen or so hosts (I don't know, I'm just guessing) per torrent. That seems unlikely to be a hot-spot to the degree that enforcing a long cache would provide a "big boost" to overall performance.

I would be surprised to learn that most routers DNS implementations enforce "a long minimum global TTL". What do you define as long by the way?

EDIT: Also, "Torrenting gets a big boost for example." sounds strange, don't trackers give out IP addresses? Why would BitTorrent be DNS bound?

> 1. Persistent DNS cache using pdnsd (even after reboot because it is on-disk) with a long minimum global TTL.

What problem does this solve? Is it a bid to improve privacy?