Bind9 "split zones"

Hi I am trying to understand bind9 more thorughly. Backstory: We have been using bind9 for a long time and overhauling it for more "usage". We have been using a "hidden master dns" logic with views for different usages. E.g. Client -> Slave DNS Server <- (Transfer zones from hidden master)

Re: Bind9 "split zones"

t; will follow the "forwarders" statement because "sub.example.com <http://sub.example.com>" has been delegated away. - Do you really want to be forwarding to your hidden primary anyway? - Why are two different servers both authoritative for "100.168.192.in-addr.arpa"?