A failover state in which one server is administratively or automatically authorized to assume broader responsibility because its peer is considered unavailable. Entering the state incorrectly can create duplicate allocation risk.
Configuration selected based on the client's network link, usually identified by GIADDR, link-address, interface, relay information, or subnet selection options.
A collection of resources from which a service selects a member. In DHCP it is an address range; in GSLB or load balancing it is a group of application endpoints.
A state in which no eligible addresses or prefixes remain for new clients. Causes include genuine growth, excessive lease duration, starvation attacks, stale leases, exclusions, or a poorly sized subnet.
An option code range reserved for local or vendor use rather than global standardization. Private-use codes can collide when devices or organizations expect different meanings.
Preboot Execution Environment, a framework that uses DHCP and a boot transfer protocol to start a system from the network. DHCP identifies architecture, boot server, and boot file or menu information.
An intermediary that forwards DHCP traffic between clients and servers on different links and supplies link or subscriber context. DHCPv4 and DHCPv6 relay formats differ.
A client indication that it no longer needs an assigned address or prefix. Because release messages can be lost, leases still require finite lifetimes and expiration handling.
The process by which a client asks to extend an existing binding before it expires. DHCPv4 normally starts renewal at T1, while DHCPv6 uses a RENEW message to the server that supplied the binding.
A configured association between a client identity and a specific address or set of options. Product semantics vary regarding whether the reserved address is inside a dynamic pool and whether it creates DNS data.
A context defining which addresses, options, or policies apply. Microsoft DHCP uses scope for an IPv4 subnet and pool, while other systems may use the term for IPv6 reachability or administrative visibility.
A DHCP option configured at a particular hierarchy level, such as server, scope, policy, reservation, or class. More-specific settings often override inherited values according to product precedence.
The amount of a DHCP scope currently leased, reserved, excluded, or available. Alerts should account for addresses that are not eligible for ordinary allocation.
A value identifying the DHCP server participating in a transaction. DHCPv4 commonly uses option 54 with an IPv4 address, while DHCPv6 uses a DUID in OPTION_SERVERID.
A DHCP option code intended for local site use. Such options can conflict across organizations and should be carefully documented when networks merge or devices move.
A legacy DHCPv4 availability design in which two independent servers each own a non-overlapping portion of a subnet's address range, often in an 80/20 ratio. DHCP failover is generally preferred when supported.
A persistent client-to-address association configured by an administrator. Products may implement it as a reservation, fixed address, manual allocation, or host object.
A typed field nested within another DHCP option, such as circuit ID inside option 82 or vendor-specific data inside an enterprise container. Its namespace is defined by the parent option.
A Microsoft DHCP grouping of multiple IPv4 scopes on the same physical network. It supports multinets where several logical subnets share one broadcast domain, but routing and client behavior must be designed carefully.
The renewal timer. DHCPv4 clients normally begin unicast renewal at T1, often 50 percent of lease time; DHCPv6 identity associations also carry T1 values.
The rebinding timer. If renewal has not succeeded by T2, the client broadens its attempt to any available server, often around 87.5 percent of DHCPv4 lease time by default.
Client information identifying a vendor, device family, or functional class. Servers use it for matching policies and returning vendor-specific configuration.
A DHCP option or nested option whose meaning is defined by a vendor or enterprise namespace. Standardized enterprise-number containers reduce collisions compared with uncoordinated private codes.