I don't really know how the config files get auto generated, but working off a guess, I manually added fake hosts in the DNS at the base of each of the ip ranges and that seems to have done the trick. It added the new reverse zones to the DNS config and dhcp can now update those reverse addresses.
This workaround is definitely hacky, but works for now.
To recap:
My network is 192.168.0.0/16. All my static hosts with actual DNS entries were under 192.168.0.0/24 and forward and reverse updates were working. I had DHCP ranges under 192.168.10.50-200 and 192.168.11.50-200 and reverse DNS updates for those were not working. I got around this by adding fake A records at 192.168.10.1 and 192.168.11.1 which got zentyal to add the proper zones to the DNS config so that DHCP updates would work.