← All posts Deutsch

How to Compare DHCP Lease Records Without Inventing a Device Timeline

A router's DHCP page can look like a short history of the network. It may list a device name, an address, a MAC address, a lease start, an expiry time, and a value such as “last seen.” When the time changes for a camera, NAS, phone, or printer, it's tempting to read that row as a timeline: the device must have disconnected at one point and returned at another.

The record usually can't tell you that much. DHCP lets a client obtain configuration, including an address and gateway. The router's table has its own refresh behavior, clock, and rules for keeping records. It may retain old entries, replace a start time after a renewal, or pull together information from DHCP, ARP, and a Wi-Fi controller. Start by saving what the table actually says. Then pair it with one independent observation.

If you first need to work out which devices and addresses are on the local network, start with How to See Every Device on Your Network and Find Its IP Address. The steps below cover comparing records over time without treating an address assignment as a complete activity log.

Time column labels

Router interfaces use similar labels for different things. “Lease time” may be the configured duration offered to a client. “Expires” normally means the future point when the assignment can be reused if it isn't renewed. “Remaining” is a countdown calculated by the router. “Last seen” may come from a separate observation by the Wi-Fi access point or a neighbor table. And “connected since” might not be DHCP data at all.

Write down the label exactly as it appears. Capture the full row, along with the router's displayed current time and timezone, if shown. A screenshot or short manual note is enough. You want to avoid comparing your computer's local clock with a router set to another timezone. Daylight-saving changes, a router without time synchronization, and rounded values in the interface can all make a difference look dramatic when there isn't one.

The rows may not all use the same source, either. A mesh system can put a wireless association time beside an address learned from DHCP. A client list might keep a friendly name from an earlier request while updating the lease expiry after a routine renewal. Check the labels and router documentation to find out what a column means. The page's appearance isn't enough.

Device identity beyond the name

Before comparing today's row with yesterday's, record more than the hostname. Clients or routers supply those names, which may be shortened or duplicated. For one candidate device, note the IP address, MAC address, client identifier if exposed, connection type, and exact time fields. If you administer the device, compare those details with its local settings or a label you control.

Pay particular attention to wireless phones and tablets. After a setting change or a recreated network profile, a private Wi-Fi address can make one physical device appear on the same network with a different MAC address. The new entry may represent a new network identity rather than a second device. A wired device’s MAC address may change after a network adapter replacement; changing its DHCP client identifier may lead to a different IP assignment.

If the identity doesn't match, keep the rows separate, even if the hostname looks familiar. State what you know: for example, “the router displays two client records with the same name but different MAC addresses.” That's an observation you can work from. “The device duplicated itself” is an explanation that needs more evidence.

Lease changes during renewal

DHCP clients commonly try to renew an assignment before it expires. The protocol defines renewal and rebinding states precisely, but a consumer router may just update the expiry time or rebuild the entire row. Neither display tells you, on its own, that the client rebooted, lost Wi-Fi, or regained power.

Consider three records taken at different times. At 08:00 a NAS in a fictional lab has address 192.0.2.20 and one hour remaining. At 09:00 the address and MAC address are unchanged, but the expiry has moved forward. That fits a routine renewal. At 10:00 the row shows a different address with the same identity. A new allocation, a router restart, a changed reservation, or a network interruption could explain it. The table alone can't tell you which.

An entry can remain after a device leaves the network, too. An unexpired lease reserves an address; it isn't a live heartbeat. A working device with a static configuration, meanwhile, may be absent from the current DHCP lease list. Address assignment and current reachability are different things. A mismatch doesn't necessarily mean the router or scanner is faulty.

Avoid forcing a release and renew just to get a clearer timestamp. That creates the event you're trying to investigate. Rebooting the router disturbs even more: it can remove logs and briefly interrupt every client. Save the existing information first, and keep the next check observational whenever possible.

An independent observation at the same moment

The next useful fact depends on what you're trying to find out. For a managed NAS that may have restarted, its own uptime or service log tells you more directly than DHCP. A switch-port link event is more relevant when you're checking whether a cable path changed. To check whether an address answers from the same subnet, a single authorized scan or neighbor-table lookup can give you another time-stamped observation.

Run that check once and note the time. A missing response doesn't settle the question. Sleeping clients, firewalls, guest isolation, VLANs, and routed subnets can all stop a particular scan from getting a reply. An ARP or neighbor entry can also outlive a response. What helps is comparing independent facts and being precise about what each one shows.

A small comparison record can contain:

  1. Router time and timezone as displayed.
  2. IP address, MAC address, client identifier, name, and all shown lease fields.
  3. Any router event-log wording that explicitly says request, renewal, expiry, or association.
  4. One independently observed result, with its time and network location.
  5. For a device you manage, a device-local uptime or application event.

Suppose a router's expiry moves at 03:15 while a NAS reports an uptime of seven days and its file service remains reachable. You can say that the router recorded a lease-related change while the observed service stayed available. If a switch port drops link and the NAS uptime resets near the same time, you have evidence for a different, still limited conclusion: the device or its network path changed during that window. You haven't yet identified a failed power supply, cable, DHCP server, or router.

Router state and network boundaries

Checking the network boundary often explains why observations disagree. A router can know about a client on one VLAN while a computer on a guest network can't reach it. A scanner on one subnet may not probe another routed subnet. With Wi-Fi client isolation, a device can be visible to the access point but unreachable from a peer. Before changing a reservation or deciding a row is stale, record the subnet and interface used for each observation.

Make sure the independent observation uses the same address as the router record, and check that the identity still matches. An address change isn't automatically suspicious. It may be expected after a router configuration change or reservation update. To use it as evidence, you need the surrounding timing and a reason to compare the records.

Don't create a reservation for a stale MAC address just to tidy up the table. A reservation can give a predictable address to the client identity that requests it. It can't fix radio coverage, establish device ownership, or prove that a named service is healthy. If you need a reservation, verify the correct current identity first. Then choose an unused address according to the router's own rules.

Conclusions supported by the record

Finish the first comparison with a statement you could check again. “At 10:05 router time, this MAC address had a lease expiring at 11:00; the device's uptime did not reset” is useful. “The device came back online at 10:05” claims something about availability and cause that those same facts don't establish.

Keeping the conclusion narrow also keeps the next action small. Inspect the router's DHCP log after the next renewal, compare the device's local uptime during the suspected window, or observe the relevant switch port once. Pick one. Refreshing the same router page over and over rarely adds new evidence.

For a longer-running local record, DeviceShelf is one possible way to note responding devices and observed addresses. Compare those observations with router records and device settings. No single view proves identity, ownership, or service availability. The aim is a modest record that helps the next check distinguish a renewal from a real connection change, rather than a perfect timeline built from one table.

Sources checked

Network tips and product updates

The occasional guide, new features and release news, straight to your inbox. No spam, unsubscribe anytime.