[knot-resolver-users] different forwarder and no cache for specific host

Hello, On my local network, I have a computer fixed IP that I would like to use a specific TLS FORWARD. Generic TLS_FORWARD is simply configured as such.     policy.add(policy.all(policy.TLS_FORWARD({                             {'9.9.9.9', hostname='dns9.quad9.net'},                 {'1.1.1.1', hostname='cloudflare-dns.com'},                 {'1.0.0.1', hostname='cloudflare-dns.com'},     }))) I tried to embed a specific different TLS_FORWARD with a     view:addr('10.10.10.10', ... ) but I cannot manage to restrict this TLS_FORWARD and to avoid it poisoning the cache. Is there somewhere an example of such setup, with ACL ending up on two different TLS_FORWARD and one with no cache ? Regards, -- Mathieu Roy