On 17/04/2018 08:44, MRob wrote:
dq.variable is certain to be necessary here just like the other example.
Only if you want to return different responses to different clients. If
all your clients are subject to the same DNS filtering policy then you
can leave the packet cache active.
__
On 2018-04-17 07:00, Brian Candler wrote:
On 17/04/2018 06:42, MRob wrote:
But this example for modifying policy actions does not set
dq.variable:
https://doc.powerdns.com/md/recursor/scripting/#modifying-policy-decisions
The documentation is very clear as to what dq.variable does: in the
sa
On 17/04/2018 06:42, MRob wrote:
But this example for modifying policy actions does not set dq.variable:
https://doc.powerdns.com/md/recursor/scripting/#modifying-policy-decisions
The documentation is very clear as to what dq.variable does: in the same
page,
https://doc.powerdns.com/md/recur
On 2018-04-17 05:42, MRob wrote:
PowerDNS blog recommends setting dq.variable when a domain response is
part of the loaded block list.
https://blog.powerdns.com/2016/01/19/efficient-optional-filtering-of-domains-in-recursor-4-0-0/
But this example for modifying policy actions does not set dq.var
PowerDNS blog recommends setting dq.variable when a domain response is
part of the loaded block list.
https://blog.powerdns.com/2016/01/19/efficient-optional-filtering-of-domains-in-recursor-4-0-0/
But this example for modifying policy actions does not set dq.variable:
https://doc.powerdns.com/m
