Does "--foreman-proxy-dns-managed true" work?

This is probably a lack of understanding on my part, but here goes... I installed my Satellite server with these commands (obfuscated a bit):

satellite-installer --scenario satellite \
--foreman-initial-organization "My Corp" \
--foreman-initial-location "My Location" \
--foreman-initial-admin-username satadmin \
--foreman-initial-admin-password obfuscated \
--foreman-proxy-tftp true \
--foreman-proxy-dhcp true \
--foreman-proxy-dhcp-gateway 10.2.225.1 \
--foreman-proxy-dhcp-nameservers 10.2.225.10 \
--foreman-proxy-dhcp-option-domain "mycorp.lan" \
--foreman-proxy-dhcp-range "10.2.225.128 10.2.225.254" \
--foreman-proxy-dhcp-search-domains "mycorp.lan" \
--foreman-proxy-dns true \
--foreman-proxy-dns-managed true \
--foreman-proxy-dns-forwarders "4.2.2.1; 8.8.8.8" \
--foreman-proxy-dns-reverse "225.2.10.in-addr.arpa" \
--foreman-proxy-dns-zone "mycorp.lan" \
--foreman-proxy-dns-server 10.2.225.10

The challenge is, even though it created the zone files I expected, when I create a new host, it does NOT update the zone files so the new hosts don't resolve. Isn't the Satellite server supposed to update the DNS zone files? I've noticed it does not, whether I spin up a new VM or even if I register an existing system. Am I misunderstanding what "--foreman-proxy-dns-managed true" does?