Lease Durations and Host Reservations
A lease duration tells a device how long it can keep its assigned IP address before it must ask the server for a renewal. Shorter leases free up addresses faster for networks with many temporary devices, while longer leases reduce renewal traffic for stable devices. Host reservations guarantee that critical devices, such as domain controllers or file servers, always receive the same IP address. The reservation links the device’s MAC address to a specific IP so the server always gives that same address, which is essential for services that rely on a fixed network identity.
Scope Options and Vendor-Specific Options
Scope-wide options apply settings to every device that receives a lease from that scope, such as the default gateway, DNS server addresses, or domain name. These options make sure all clients on a subnet have the same network configuration without manual setup. Vendor-specific options go further by targeting devices from a particular manufacturer, allowing the DHCP server to send custom settings, like a specific VLAN tag or boot server address, only to certain hardware types. Both options are applied at the scope level and are sent along with the IP lease.
Validating Client IP Assignment
Validation ensures that clients in both on-premises subnets and Azure-connected subnets get the correct IP configuration. You can check the DHCP server logs, lease records, and address usage reports to see if devices are receiving the expected addresses and options. In a hybrid environment, a client on an Azure-connected subnet must still be able to reach the on-premises DHCP server or a DHCP relay agent for the assignment to work. Regular validation catches misconfigurations early, such as overlapping scopes or missing options, keeping the network reliable across all locations.