Re: DNS_RRL_MAX_RATE defines 1000

在 2020年7月10日 +0800 AM2:11，Tony Finch ，写道： > Zhiyong Cheng wrote: > > > > We are using named cluster in our internal network as the authoritative > > DNS. So there are no cache servers between clients and named cluster. > > Maybe we should add one but it is just another story. > > Sorry, I wasn't c

Re: DNS_RRL_MAX_RATE defines 1000

Zhiyong Cheng wrote: > > We are using named cluster in our internal network as the authoritative > DNS. So there are no cache servers between clients and named cluster. > Maybe we should add one but it is just another story. Sorry, I wasn't completely clear: I was not saying that your authoritati

Re: DNS_RRL_MAX_RATE defines 1000

Thanks for this reply : ) We are using named cluster in our internal network as the authoritative DNS. So there are no cache servers between clients and named cluster. Maybe we should add one but it is just another story. There was a strange thing when I tested RRL using queryperf.  I generated

Re: DNS_RRL_MAX_RATE defines 1000

程智勇 wrote: > > So could anybody tell me why DNS_RRL_MAX_RATE defined 1000? RRL is designed for authoritative DNS servers. Legitimate queries come from recursive resolvers with caches. There should not be more than one query for each RRset from each resolver per TTL. So a normal response rate limi

DNS_RRL_MAX_RATE defines 1000

Hi, all I deployed a cluster of DNS which combined with a master and two slaves recently. I opened the response rate limiting function in slaves, which parameters like below: rate-limit {     ipv4-prefix-length 32;     responses-per-second 250;     all-per-second 1000;     min-table-size 10