Verifying DHCP lease timers on a Cisco IOS or IOS XE router requires checking two different places depending on what you need to know: the active binding database (which tracks when each connected client’s current lease expires) and the running configuration (which defines the total lease duration assigned to a pool). Furthermore, if the router itself acts as a DHCP client on an external WAN interface, it stores that ISP-assigned lease in a separate table entirely.
This guide walks through the exact Cisco CLI commands to inspect active client expiration timestamps, verify default and custom pool durations, check WAN client leases, and adjust or reset bindings when troubleshooting network address exhaustion.
Table of Contents
How to Check Configured DHCP Lease Duration and Active Bindings
When a Cisco router acts as a DHCP server, no single command displays both the configured pool timer and the remaining time for active clients. Follow these steps in privileged EXEC mode (#) to inspect both values accurately.
Step 1: Verify the Router System Clock
Before inspecting active lease expirations, confirm the router’s internal clock is accurate. Cisco IOS records lease expirations as absolute timestamps rather than countdown timers.
Router# show clock
08:15:22.419 UTC Tue Nov 17 2026
Step 2: Check Active Client Lease Expiration Timestamps
Run show ip dhcp binding to view all active IP leases alongside their exact expiration dates and times. You can also append a specific IPv4 address (for example, show ip dhcp binding 192.168.10.12) to inspect a single host.
Router# show ip dhcp binding
Bindings from all pools not associated with VRF:
IP address Client-ID/ Lease expiration Type State Interface
Hardware address/
User name
192.168.10.11 0100.5056.9a12.34 Nov 18 2026 04:12 AM Automatic Active GigabitEthernet0/1
192.168.10.12 0100.5056.9a56.78 Nov 18 2026 07:45 AM Automatic Active GigabitEthernet0/1
192.168.10.50 0100.5056.9a99.00 Infinite Manual Active GigabitEthernet0/1
To determine a client’s remaining lease time, compare the timestamp in the Lease expiration column against the current output from show clock.
Step 3: Check the Configured Pool Lease Duration
Because show ip dhcp pool displays address utilization statistics rather than timer settings, inspect the running configuration filtered to the DHCP section to view the configured lease duration for each pool:
Router# show running-config | section ip dhcp pool
ip dhcp pool LAN_POOL
network 192.168.10.0 255.255.255.0
default-router 192.168.10.1
dns-server 8.8.8.8 1.1.1.1
lease 3 12 30
In the lease <days> [<hours>] [<minutes>] output above, lease 3 12 30 indicates that clients in LAN_POOL receive a lease duration of 3 days, 12 hours, and 30 minutes.
Key Takeaway: Always pair show ip dhcp binding (for per-client expiration timestamps) with show running-config | section ip dhcp pool (for the pool’s configured lease length).
While inspecting the running configuration works for custom timers, administrators often find that the lease line is completely absent from the pool configuration. Understanding Cisco’s default behavior explains why this occurs.
Frequently Asked Questions About Default Cisco DHCP Lease Times
What is the default DHCP lease time on a Cisco router?
By default, Cisco IOS and IOS XE assign a DHCP lease duration of 1 day (24 hours / 1,440 minutes / 86,400 seconds) to every dynamic address pool.
Why does no lease command appear under ip dhcp pool in show running-config?
Cisco IOS suppresses default parameter values in standard show running-config output to keep configurations concise. If a pool uses the default 24-hour lease—either because a lease command was never entered or because it was manually set to lease 1—the router hides the lease line from the standard configuration view.
How can I verify the default lease setting in the CLI if it is hidden?
Use the all keyword with show running-config to force the router to display all hidden default parameters alongside custom settings:
Router# show running-config all | section ip dhcp pool
ip dhcp pool VOICE_POOL
network 192.168.20.0 255.255.255.0
default-router 192.168.20.1
lease 1
When do clients renew a default 24-hour Cisco DHCP lease?
Under the 24-hour default, clients attempt to renew their lease with the Cisco router at the T1 timer (50% of the lease duration, or 12 hours). If the router does not respond, the client broadcasts a rebind request at the T2 timer (87.5% of the lease duration, or 21 hours).
Key Takeaway: If no lease statement appears under your DHCP pool configuration, the pool is actively enforcing a 24-hour lease duration.
The commands above apply when your Cisco router serves IP addresses to internal LAN hosts. However, if your router obtains its own public IP address dynamically from an ISP on an external interface, you must query the DHCP client process instead.
Checking DHCP Client Lease Time on a Router WAN Interface
When a router interface is configured with ip address dhcp, use show dhcp lease in privileged EXEC mode to check the ISP-assigned lease duration, renewal timers, and remaining time until the next renewal attempt:
! Verify DHCP client lease parameters on a WAN interface
Router# show dhcp lease
Temp IP addr: 203.0.113.45 for peer on Interface: GigabitEthernet0/0/0
Temp sub net mask: 255.255.255.0
DHCP Lease server: 203.0.113.1, state: 5 Bound
DHCP transaction id: 1A4F
Lease: 86400 secs, Renewal: 43200 secs, Rebind: 75600 secs
Temp default-gateway addr: 203.0.113.1
Next timer fires after: 09:14:22
Retry count: 0 Client-ID: cisco-001e.f72a.b100-Gi0/0/0
Client-ID hex dump: 636973636F2D303031652E663732612E
623130302D4769302F302F30
Hostname: Router
! Quick reference for interpreting timer fields:
! Lease: Total lease duration granted by the ISP (in seconds)
! Renewal: T1 timer (seconds from assignment until unicast renewal)
! Rebind: T2 timer (seconds from assignment until broadcast rebind)
! Next timer fires after: Exact countdown (HH:MM:SS) until the next renewal attempt
Key Takeaway: Use show dhcp lease whenever the Cisco router itself is the DHCP client on a WAN port, as WAN leases are excluded from show ip dhcp binding.
Once you have audited your router’s DHCP lease times, you may find that the default 24-hour window is too long for a high-turnover guest Wi-Fi network or too short for fixed infrastructure.
How to Change the DHCP Lease Time on a Cisco Router
Modifying the lease duration requires updating the specific DHCP pool in global configuration mode. Follow these steps to lengthen, shorten, or permanently lock a pool’s lease timer.
Step 1: Enter Global Configuration Mode
Access privileged EXEC mode and open configuration mode:
Router# configure terminal
Step 2: Select the Target DHCP Pool
Enter DHCP pool configuration mode for the pool you identified earlier:
Router(config)# ip dhcp pool LAN_POOL
Step 3: Set the New Lease Duration
Use the lease command in the format lease {days [hours [minutes]] | infinite}. Because hours and minutes are positional arguments, you must enter 0 for days (and 0 for hours) when configuring sub-day leases:
- Set a multi-day lease (e.g., 7 days):
text
Router(dhcp-config)# lease 7 - Set an hour-based lease for guest networks (e.g., 0 days, 4 hours):
text
Router(dhcp-config)# lease 0 4 - Set a minute-based lease for lab testing (e.g., 0 days, 0 hours, 30 minutes):
text
Router(dhcp-config)# lease 0 0 30 - Set a permanent lease that never expires:
text
Router(dhcp-config)# lease infinite
Step 4: Exit and Save the Configuration
Return to privileged EXEC mode and write the changes to NVRAM:
Router(dhcp-config)# end
Router# write memory
Key Takeaway: New lease settings apply immediately to new DHCP discoveries and future client renewals, but existing active clients retain their previously assigned expiration timestamps until their next renewal cycle.
Because active clients keep their old expiration timers until T1 renewal, shortening a lease time will not immediately free up IP addresses in a depleted subnet. To reclaim addresses right away, you must manually clear the router’s binding database.
How to Clear and Reset DHCP Leases on a Cisco Router
When a DHCP pool runs out of available IP addresses or stale bindings fail to release properly, follow this workflow to clear the bindings and return quarantined addresses to the active pool.
Step 1: Check for Quarantined IP Conflicts
Before wiping active bindings, check whether the router has removed IP addresses from the assignable pool due to ping or gratuitous ARP conflicts:
Router# show ip dhcp conflict
IP address Detection method Detection time VRF
192.168.10.15 Ping Nov 17 2026 06:10 AM
192.168.10.22 Gratuitous ARP Nov 17 2026 07:05 AM
Any IP listed in show ip dhcp conflict is locked out of the DHCP pool until manually cleared.
Step 2: Clear Specific or All Active DHCP Bindings
Use clear ip dhcp binding in privileged EXEC mode to delete lease records from the router’s database:
- Clear a single client’s lease:
text
Router# clear ip dhcp binding 192.168.10.11 - Clear all dynamic leases across the router:
text
Router# clear ip dhcp binding * - Clear all dynamic leases within a specific VRF:
text
Router# clear ip dhcp binding vrf GUEST_VRF *
Note: Clearing a binding on the Cisco router deletes the server record immediately, though it does not send a revocation packet to the endpoint unless the client initiates a renewal or reconnects to the network.
Step 3: Clear the DHCP Conflict Database
If Step 1 revealed conflicted addresses that are no longer in use by static hosts, clear the conflict table so the DHCP server can lease those IP addresses again:
Router# clear ip dhcp conflict *
Key Takeaway: Combining clear ip dhcp binding * with clear ip dhcp conflict * resets the router’s dynamic address tracking and immediately reclaims stranded IP addresses.
For network engineers building automated parsing scripts or looking up exact field behaviors across IOS releases, the reference section below details the formal syntax and output definitions for Cisco’s DHCP verification commands.
Cisco IOS DHCP Verification Command Reference
The following specifications summarize the syntax, command modes, and output fields defined in the official Cisco IOS and IOS XE command reference documentation.
Command Syntax and Modes
| Command | Command Mode | Syntax Description |
|---|---|---|
show ip dhcp binding [ip-address] | User EXEC (>) or Privileged EXEC (#) | Displays address bindings on the Cisco IOS DHCP server. Specify ip-address to filter output to a single host entry. |
show dhcp lease | Privileged EXEC (#) | Displays current DHCP lease parameters obtained by the router on interfaces configured as a DHCP client. |
clear ip dhcp binding [vrf vrf-name] {address \| *} | Privileged EXEC (#) | Deletes an automatic address binding (address) or all automatic address bindings (*) from the DHCP server database. |
Output Field Descriptions (show ip dhcp binding)
IP address: The IPv4 address assigned to the client from the local DHCP pool.Client-ID/Hardware address/User name: The unique client identifier (typically prepended with media type01for Ethernet followed by the MAC address) or raw hardware MAC address if no DHCP option 61 Client-ID was provided.Lease expiration: The calendar date and clock time (Month Day Year HH:MM AM/PM) when the lease expires, orInfinitefor manual static bindings and pools configured withlease infinite.Type: The assignment method (Automaticfor dynamic pool allocations,Manualfor static host bindings defined viahostandclient-identifier/hardware-address).State: Current binding lifecycle state (Activefor completed ACK bindings,Selectingduring initial offer negotiation).Interface: The local router ingress interface through which the client request was received.
Official Documentation References
For platform-specific release notes, SNMP trap integration, and VRF-aware DHCP relay configurations, consult the following official Cisco publications:
* Cisco IOS IP Addressing Services Command Reference: Covers complete syntax trees and history for show ip dhcp binding, show dhcp lease, lease, and clear ip dhcp binding.
* Cisco IOS XE IP Addressing Services Configuration Guide: Provides architectural guidelines for configuring the Cisco IOS DHCP Server, DHCP Client, and database agents for persistent binding storage across reboots.
Key Takeaway: Reference the Type and State fields in show ip dhcp binding alongside the official Cisco IOS IP Addressing Services Command Reference to distinguish between transient negotiation states, dynamic leases, and permanent manual reservations.
Managing DHCP lease times on a Cisco router comes down to matching the right command to the router’s role. Use show ip dhcp binding and show running-config | section ip dhcp pool (or show running-config all | section ip dhcp pool when using the 24-hour default) to monitor the router’s internal DHCP server, and rely on show dhcp lease to track external ISP leases on WAN interfaces. When network demands change, adjusting the lease command under the pool configuration and clearing stale bindings with clear ip dhcp binding ensures your IP address space remains healthy and responsive.











Comments