Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refine DNS rule for bottleneck #107

Open
taoeffect opened this issue Jan 21, 2015 · 0 comments
Open

Refine DNS rule for bottleneck #107

taoeffect opened this issue Jan 21, 2015 · 0 comments

Comments

@taoeffect
Copy link
Member

taoeffect commented Jan 21, 2015

For now we're solving #103 with a slightly imperfect solution of looking at first character of subdomain.

A "perfect" solution to the problem that @SGrondin said to put on TODO is the following:

keep track of how many subdomains are being queried on that domain

then throttle each domain by the number of subdomains that have been queried. For example, citizenswebforum.com had like at least 50 subdomains iterated over in short period, then throttle everything going to citizenswebforum.com

(obviously treat all subdomain levels as a single subdomain, i.e. asdf.www should logically be treated as one subdomain, not two)

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/7918764-refine-dns-rule-for-bottleneck?utm_campaign=plugin&utm_content=tracker%2F528702&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F528702&utm_medium=issues&utm_source=github).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants