I recently sent a large amount of traffic towards 1.1.1.1 (from a single IP.)
When we reached around 10 requests per second it seems that we hit some type of rate limit as our queries where dropped.
Is there any way around this?
1.1.1.1 - Rate Limiting
If there ist a rate limit, it’s there for a good reason i would guess
1 Like
Only have this issue with Cloudflare, google and quad9 do not rate limit at all. 10 queries a second is not exactly a lot.
Yes, use multiple IPs 
Btw, I tested this as well and I couldn’t hit the limit.
I will retest and let you know about the results.
So I run my little benchmark for 31.71 seconds, made 1995 DNS requests, from which 97.64% was successful and 2.31% failed (could be because of my poor ISP).
Concurrency level was 30.
I tested against 1.1.1.1
Runtime: 31.7168600559 sec.
Total tested: 1995 [ 100 % ]
Good: 1948 [ 97.64 % ]
Failed: 46 [ 2.31 % ]
Avg speed: 0.0574952833037
It seems unlikely Cloudflare would block at a query rate of 10qps. How/ what are you testing? What error do you receive?
-OG
Google has (had?) a rate limit of 100 queries per second.
Quad9… I want to say that they have rate limits that can’t be described with a single number, but I can’t find a reference.
I just want to clarify something, are you sending 10 identical queries per second or 10 unique queries per second?
2 Likes
For Google reference was 500 QPS; That limit was lowered down, after Cloudflare launched 1.1.1.1
In my test I was sending random queries per second.
And also I was performing ‘control’ checks every 2nd query, in order to be sure that everything is in line.
I will share code later
1 Like
You can perform tests of your DNS servers with this piece of Python code I wrote:
We do not rate limit. You should be able to send 10QPS pretty easily.
3 Likes