How to configure a BIND 9 name server as a slave for a zone that exists in multiple views?

I have a Bind9 hidden primary configured with views, and I need a secondary to transfer all the views of the same zone. Example: On **primary**: view "dmz-view" { match-clients { server-dmz; }; allow-transfer { transfer-dmz; }; recursion yes; allow-query-cache { server-dmz; }; zone "example.com" IN { type master; file "/var/cache/bind/db.dmz.example.com"; notify yes; }; }; view "untrust-view" { allow-query { any; }; allow-transfer { transfer-untrust; }; recursion no; zone "example.com" IN { type master; file "/var/cache/bind/db.untrust.example.com"; notify yes; }; }; Now, my problem is that if I put the secondary's IP in both acls (transfer-dmz and transfer-untrust), it will match the first view and will transfer only that. I've read examples 3,4 in https://kb.isc.org/docs/aa-00851 but it doesn't seem to fit my needs (or am I misunderstanding?) I also read https://flylib.com/books/en/2.684.1/setting_up_a_slave_name_server_for_a_zone_in_multiple_views.html but since it's aged I suppose it's outdated . Any cookbook or advice?