Hi,
am I reading the unbound documentation correctly if I conclude
that I currently cannot limit the application of rpz to only
those clients which fall within a specified view?
If that's correct, #wishlist.
Best regards,
- Håvard
Hi,
am I reading the unbound documentation correctly if I conclude
that I currently cannot limit the application of rpz to only
those clients which fall within a specified view?
If that's correct, #wishlist.
Best regards,
- Håvard
Hi Håvard,
That is correct.
If it fits your configuration, you could limit the rpz with tags though.
Either client IP based (access-control-tag:) or listening interface based (interface-tag:).
Best regards,
-- Yorgos
That is correct.
If it fits your configuration, you could limit the rpz with tags
though.
Either client IP based (access-control-tag:) or listening interface
based (interface-tag:).
Thanks, it looks like something based on access-control-tag:
would be sufficient in this case. Somehow I had managed to
overlook the "tags:" entry in the RPZ section of the man page.
Best regards,
- Håvard