* Remi Gacogne [190712 16:08]:
> That would make it possible to do something like that in a generic way:
>
> addAction({ 'rate1.com','a.aa' }, ContinueAction(PoolAction("static")))
>
> I don't think it would be too complicated to implement and since it
> would be self-contained we could even
Am 12.07.2019 um 16:08 schrieb Remi Gacogne:
>
>
> On 7/12/19 2:52 PM, Klaus Darilion wrote:
>> That does not work. At the moment, if I want to add another domain (ie
>> rate1.com) to the "static" pool I have to check first, if the domain is
>> rate limited or not, and if yes, use a andAction c
On 7/12/19 2:52 PM, Klaus Darilion wrote:
> That does not work. At the moment, if I want to add another domain (ie
> rate1.com) to the "static" pool I have to check first, if the domain is
> rate limited or not, and if yes, use a andAction construct to achieve my
> goal. So, yes it would be possi
Hi Peter!
My current config is:
-- Send requests for zones without dynamic features to pool "static" (NSD)
-- For other zones forwarded to default pool (PDNS)
addAction({ 'a.aa' }, PoolAction("static"))
-- Rate limiting for domains
addAction(QNameRule("rate1.com"), AllowAction())
addAction(
Hi Klaus,
On 7/12/19 10:34 AM, Klaus Darilion wrote:
> I have a ruleset with severals whitelist (AllowAction) and ratelimit
> (MaxQPSRule+DropAction).
>
> Now, independent of these rules I would like to use different backend
> pools. But now I have a problem as PoolAction() immediately forwards t
Hello!
I have a ruleset with severals whitelist (AllowAction) and ratelimit
(MaxQPSRule+DropAction).
Now, independent of these rules I would like to use different backend
pools. But now I have a problem as PoolAction() immediately forwards the
request and my blacklist/whitelist rules are not hand
