pjhtech Tools
MikroTik · RouterOS v7

MikroTik DHCP Commands: Leases, Pools and Options

Quick answer #

Read /ip/dhcp-server/lease for addresses assigned by this router, /ip/pool/used for current pool allocations, and /ip/dhcp-server/network for client options. If the MikroTik receives its own WAN address by DHCP, inspect /ip/dhcp-client instead. Server and client menus describe opposite sides of the DHCP relationship.

Scope: RouterOS v7 on RouterBOARD, CCR, CRS running RouterOS, or CHR where the relevant feature exists. Not SwOS. Output fields depend on release and hardware. This page covers DHCPv4; DHCPv6 uses different menus and behaviour.

Commands #

The MAC address is an example. These commands inspect leases and settings without removing assignments or renewing the WAN connection.

Commands
RouterOS v7 · RouterOS v7 terminal; absolute menu paths

Read-only
/ip/dhcp-server/print detail
Read-only
/ip/dhcp-server/lease/print detail
Read-only

Replace these example values: 02:00:00:00:00:10.

/ip/dhcp-server/lease/print detail where mac-address=02:00:00:00:00:10
Read-only
/ip/dhcp-server/network/print detail
Read-only
/ip/pool/print detail
Read-only
/ip/pool/used/print
Read-only
/ip/dhcp-client/print detail
Read-only
/log/print where topics~"dhcp"
Output may contain sensitive operational data.

Read the result #

A bound server lease is evidence that the server has assigned an address to a client. It does not prove that the client's VLAN, DNS or application access is working. Check the active address and identifier rather than relying only on a friendly hostname supplied by the endpoint.

Compare the lease's server with that server's interface and address pool. Then inspect the matching network entry for gateway and DNS information. This separates address allocation from the options the client receives. A client with the wrong DNS server can appear to have an Internet outage even though DHCP and basic IP forwarding work.

The pool view helps explain exhaustion. Its configured range defines available space, while the used view identifies allocations. Avoid estimating capacity from the subnet size alone: exclusions, static reservations and other consumers can make that estimate misleading.

Investigate one client #

Start with the client's currently reported MAC address, particularly if it uses a private Wi-Fi address. Record the lease state, server, active address and the last observed attempt. Compare a working client on the same VLAN with the affected one. A comparison on another VLAN is less useful because it may use another pool and option set.

If no matching lease appears during a fresh request, follow the request path through the access port, VLAN and any relay. If a lease appears but applications fail, test the gateway and DNS path separately. If the router's WAN DHCP client is the failing component, keep that separate from LAN lease troubleshooting.

Pitfalls #

Deleting all leases is not an inspection step. It can make the evidence less clear and does not force every endpoint to immediately request a new address. Likewise, releasing the router's WAN lease may disconnect the management session.

A reserved address deserves the same conflict checks as any other planned static allocation. Keep the DHCP evidence with the VLAN and address-plan record so that a later pool expansion does not reuse infrastructure addresses accidentally.

Sources

Documentation reviewed: 8 October 2026