/
Best Practices for Configuring DHCP
Document toolboxDocument toolbox

Best Practices for Configuring DHCP

Owned by Sri Raghu
Last updated: Sept 06, 2024
2 min read

This section lists important information about the behavior and outcomes of various operations related to IPAM/DHCP objects. 

Copying Objects

  • When you perform a copy operation on an IP space, address block, or subnet, a new copy of these respective objects is created. Both the existing and the newly copied objects will exist in IPAM until you manually delete them.

  • The DHCP lease data (as available in IPAM) is not copied into the newly created IP space, address block, or subnet.

  • Also, the DHCP server does not delete its on-prem lease database until the expiration time.

Moving Objects to Recycle Bin

  • When you move an IP Space, address block, subnet, or range to recycle bin, lease data will be deleted in the Infoblox Portal (IPAM).

  • However, DHCP lease data is not deleted from the DHCP server and in the cloud. This means that the DHCP server will continue to expire the current leases in its database.

Restoring Objects from Recycle Bin

  • When you restore IPAM/DHCP objects from the recycle bin, as mentioned in the above scenario leases will be deleted from the Infoblox Portal and you cannot restore leases again.

Resetting Objects to Factory Settings

  • When you perform a factory reset, the DHCP server deletes lease information from its on-prem lease database.

Restarting a Service or deleting a Service Instance

  • Other operations such as a service restart, deleting the service instance, and rebooting the NIOS-X Server will lead to the DHCP server retaining its on-prem lease database until the expiration time.

Other recommendations

  • To ensure minimum service interruption to the end users, we recommend you manually clear leases from the CSP or through an API or wait until the lease expires on the client before you proceed with the operations mentioned above.