A lease state used when a DHCP server believes an address is already in use or has failed conflict detection. The server normally avoids offering that address until an administrator clears the state or the implementation retries it.
A lease currently assigned to a client and not yet expired, released, or invalidated. The lease database normally records the address, client identifier, start time, duration, and state.
A protocol mechanism that streams DHCP lease state changes to a requesting system after an initial synchronization. It is commonly used by access, security, accounting, or IPAM systems that need near-real-time binding information.
The process of selecting an address or prefix from a larger pool and making it available for use. Allocation does not always mean the address has been configured on a device yet.
A condition in which two interfaces attempt to use the same IP address on the same logical network. Symptoms can include intermittent connectivity, ARP or Neighbor Discovery instability, and DHCP declines.
A set of addresses available for dynamic allocation. A pool is normally associated with a subnet or link and may be restricted by policies, classes, exclusions, or utilization thresholds.
A policy that associates a particular address with a known client identity so the server consistently offers that address. Some products distinguish a reservation from a fixed address that sits outside a dynamic pool.
An ARP-based check used before assigning or using an IPv4 address to determine whether another device appears to claim it. DHCP servers or clients may use probes as part of conflict detection.
A Microsoft Active Directory control that allows approved DHCP servers to provide service in an AD domain environment. An unauthorized Windows DHCP server may stop serving clients.
An allocation method in which DHCP permanently assigns an address to a client from a pool, rather than leasing it for a limited period. Dynamic allocation is far more common.
The association between a client and configuration state, especially an assigned address or delegated prefix. A binding can include identity, lifetimes, options, and server ownership.
The persistent or replicated data store holding leases, reservations, identifiers, lifetimes, and states. Its consistency is critical during restart and failover.
The Bootstrap Protocol, a predecessor to DHCP used to provide startup configuration and boot information. DHCP preserves the BOOTP message format and extends it with leases and options.
A server that supplies initial network or boot configuration to a client. Depending on context, it may be a DHCP server, TFTP server, HTTP boot server, or provisioning controller.
Delivery to all hosts on a local broadcast domain. DHCPv4 clients initially use broadcasts because they may not yet know their address, server, or default gateway.
A mechanism for retrieving a large set of DHCP lease or binding data efficiently, often after a collector restarts. It is used by relay agents, access devices, accounting systems, and IPAM integrations.
A classification used to apply DHCP policy based on information such as vendor class, user class, relay information, architecture, or custom expressions. Classes can select pools, options, lease times, or access rules.
A DHCP option by which a client communicates its desired fully qualified domain name and dynamic-update preferences. The server can use it to coordinate forward and reverse DNS registration.
An identifier supplied by a DHCP client so the server can recognize it independently of the current link-layer address. DHCPv4 uses option 61, while DHCPv6 primarily uses a DUID.
The defined sequence of client states and transitions used to acquire, renew, rebind, release, or validate configuration. DHCPv4 examples include INIT, SELECTING, REQUESTING, BOUND, RENEWING, and REBINDING.
A check performed before or around address assignment to see whether an address is already in use. DHCPv4 may use ICMP echo, ARP probes, or client feedback, while IPv6 clients use Duplicate Address Detection.
Dynamic DNS, the controlled creation, modification, or deletion of DNS records without manually editing a zone file. DHCP servers and clients commonly use DNS UPDATE to register address and pointer records.
A client message indicating that an offered or assigned address appears to be in use. The server normally marks the address unavailable for investigation or later retry.
A DNS record that stores a digest representing a DHCP client identity and name association. It helps DHCP servers detect ownership conflicts during coordinated dynamic DNS updates.