DDNS Update on DHCP Renew. It was designed for situations where Infoblox is running DHCP and Microsoft is the DNS server. Microsoft DNS scavenging only uses one parameter - time of last dynamic update. So the client needs to update every time it renews its lease, or it risks having its record scavenged. It is also often needed when clients are regularly switching between interfaces, such as moving from the docking station to the wireless network and back again, while leases are active on both networks with the same hostname but with different MAC addresses.

DHCP can be impacted by seperate DNS appliances. DHCP pauses lease issuing until a DDNS update is completed.

The DNS server is single threaded. So it pauses when doing an DDNS update. If you have thousands of DDNS updates happening, this can impact recursive DNS if it is happening on the same box as the DDNS updates.

This is why a hidden primary (internal) is useful if internal authoratative is the first layer of recursion. However, you can also have the recursive servers forward internallay as required.

There is no reason to enable “Update DNS on DHCP Lease Renewal”. This feature is already implemented in BIND with the deferred update mechanism. If a DDNS update is lost for some reason, it will be requeued and re-attempted later. Which is basically also what the “Update on Lease Renewal” feature does

Palo Alto Networks Prisma Access supports DDNS and the documentation is here.