Disabling RPZ for a few clients / views sharing zones

[Chuck Anderson]

What is the best way to disable RPZ for a few clients (without forcing
those clients to use different DNS server IPs)?  I think I could
create a new view that has all the same zones and zone contents except
for the RPZ one.  If I go this route, is it still required to set up
per-view IP aliases on the master and slaves so that NOTIFY and
transfers work properly?  All of my client-facing DNS servers are
secondaries with a shadow master.  I was kinda hoping that newer
versions of BIND could share zones (with identical zone contents)
between views without requiring the messy multiple IP alias setup.

Thanks.