You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When qBittorrent starts and loads a large number of torrents, it will generate a large number of DNS queries very quickly (thousands per second). Some DNS servers (e.g. Pi-hole) have a rate limiting feature, and may start to throttle the computer's DNS queries (refuse to answer) as a result. In one case this resulted in 45 minutes of no DNS queries answered.
It would be nice if there was a possibility to limit the rate of DNS queries. This could be implemented with a queue, where a thread would retrieve queries at a set rate from the queue and send them out to the DNS server. This could result in delaying the start of downloading and seeding, because until a tracker's DNS name is resolved, it can't be contacted.
Use case
Limit the rate of DNS queries (especially at startup) to avoid triggering DNS servers with rate limit enforcement.
Suggestion
When qBittorrent starts and loads a large number of torrents, it will generate a large number of DNS queries very quickly (thousands per second). Some DNS servers (e.g. Pi-hole) have a rate limiting feature, and may start to throttle the computer's DNS queries (refuse to answer) as a result. In one case this resulted in 45 minutes of no DNS queries answered.
It would be nice if there was a possibility to limit the rate of DNS queries. This could be implemented with a queue, where a thread would retrieve queries at a set rate from the queue and send them out to the DNS server. This could result in delaying the start of downloading and seeding, because until a tracker's DNS name is resolved, it can't be contacted.
Use case
Limit the rate of DNS queries (especially at startup) to avoid triggering DNS servers with rate limit enforcement.
Extra info/examples/attachments
Pi-hole rate limit documentation
The text was updated successfully, but these errors were encountered: