mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Limit the rate of DNS queries #16560
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#16560
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Bu11etmagnet on GitHub (Jan 23, 2025).
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
@stalkerok commented on GitHub (Jan 24, 2025):
Max http announces in advanced settings
@xavier2k6 commented on GitHub (May 25, 2025):
ANNOUNCEMENT!
For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:
Please select/click the 👍 &/or ❤
reactionsin the original/opening post of this ticket.Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)
DO:
DO NOT:
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)
@SignFinder commented on GitHub (Nov 4, 2025):
Good idea. Sometimes qbittorrent-nox generates huge amount of dns queries and router stops working.
@wolfsilver00 commented on GitHub (Jan 9, 2026):
Im finding this issue with qbittorrent-nox too. Using my self-hosted DNS I can see that it spams queries for all trackers constantly, at least once a second
@SignFinder commented on GitHub (Jan 28, 2026):
Let me share more might useful information.
Connection\ResolvePeerCountries=false
Connection\ResolvePeerHostNames=false
But uploaded torrents sometimes generate a large amount to DNS server.
For example - quad9 public dns server limits DNS queries when ~30+ active torrents are in upload state