-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
Implement rate-limit for outgoing requests #1382
Labels
Comments
Does configuring the bootstrap DNS server to something else workaround the issue? |
Yes, configuring it to Google DNS alleviates the problem. |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
I'm using
1.1.1.1
as my upstream as follows:Whenever I restart the
blocky
container I run afoul of CloudFlare's 10QPS limit because all the devices on the network are simultaneously requesting IPs. To counter this, I have had to putblocky
behinddnsmasq
and on every restart I have to first switchdnsmasq
to use Google DNS, then startblocky
and finally onceblocky
shows that it can handle queries I switchdnsmasq
to use blocky.Do note that this happens only when the
blocky
DNS server has been down for ~30mins or so and the network doesn't have any DNS resolvers which causes devices to retry queries and hence builds up the query volume.Relevant Links
The Ask
It will be helpful if
blocky
can be configured to not exceed a given QPS limit on a global level. Something along the lines of follows:This would make cold-starts of blocky much easier.
The text was updated successfully, but these errors were encountered: