Why Do IP Address Conflicts Return After a Home Router Restart?

Eva Wong

IceWhale author

Eva Wong is the Technical Writer and resident tinkerer at ZimaSpace. A lifelong geek with a passion for homelabs and open-source software, she specializes in translating complex technical concepts into accessible, hands-on guides. Eva believes that self-hosting should be fun, not intimidating. Through her tutorials, she empowers the community to demystify hardware setups, from building their first NAS to mastering Docker containers.

Why Do IP Address Conflicts Return After a Home Router Restart? - Zima Store Online

An IP conflict returns after a router restart when two devices or two address-allocation systems still believe they own the same address.

In a home NAS network, the reboot often exposes a hidden overlap rather than creating a random new fault. The router rebuilds DHCP state, sleeping devices reconnect in a different order, manually assigned addresses remain active, reservations may bind to another MAC, and a second router or access point may begin offering leases. The correct fix is to identify both claimants and repair the allocation rule before clearing caches or rebooting everything again.

Confirm the Conflict With Two MAC Addresses

Record the conflicting IP, the NAS MAC address, the router’s current lease entry, and the MAC shown in the client ARP or neighbor table. Repeat the check immediately after the warning appears rather than relying on an older screenshot.

A Synology community diagnosis explains that a NAS conflict usually means the manually chosen address sits inside the DHCP scope without a matching reservation, allowing the router to assign it again to another interface or device.

If the same IP alternates between two MAC addresses, identify both physical devices before changing settings. If only one MAC appears, inspect whether the NAS has multiple interfaces, a bond, a virtual bridge, or a randomized client MAC that makes one device look like several identities.

Check for a Static Address Inside the DHCP Pool

Compare every manually configured server, printer, camera, access point, and smart-home address with the router’s dynamic pool. A static address is not protected merely because no conflict existed before the reboot.

A real home-network case describes a smart device taking the NAS address while the NAS was powered off, because the router still considered that address available. The conflict returned when the NAS came back and reclaimed its manual address.

Choose one allocation model: either use router-side DHCP reservations for infrastructure devices, or place documented static addresses outside the dynamic pool. Do not configure a static address and assume an unrelated reservation elsewhere will automatically protect it.

Check Whether the Router Preserves Leases Across Reboots

Inspect the lease table before and after a controlled router restart. Note whether the router restores prior leases, discards them, or immediately offers addresses before all reserved and static devices are visible.

Netgear users documented routers where DHCP leases were not persistent and connected devices began reusing addresses after each reboot.

If the router loses dynamic lease history, reservations become more important for the NAS and other fixed services. Update firmware when appropriate, shorten the test to one reboot and two devices, and replace the router only after proving the conflict follows its lease-rebuild behavior.

-15% OFF

ZimaBoard 2 - Mini Home Server for Your Big Idea

Single board computer zimaboard2

Look for a Second DHCP Server or Overlapping Scope

Capture or inspect DHCP offers from a newly connecting client after the restart. A mesh node, old router, Wi-Fi extender, virtual router, container, or lab server can begin answering before the intended gateway is fully online.

IP-management guidance identifies overlapping scopes and inconsistent lease records between multiple DHCP servers as common causes of duplicate address allocation.

Disable DHCP on every device except the intended server, or define non-overlapping scopes when multiple servers are deliberate. Verify from a client packet capture or lease details that only the expected server identifier issues the address.

Check Reservations Against the MAC Address That Actually Reconnects

A reservation works only when the device requests a lease using the MAC address stored in the router. Wi-Fi privacy addresses, USB adapters, bonded ports, replaced NICs, virtual bridges, and dual Ethernet interfaces can change the identity seen by DHCP.

Home-network troubleshooting guidance notes that recurring conflicts can involve duplicate leases, static overlap, or ARP table changes after network equipment or interfaces change.

Match the reservation to the active NAS interface and remove stale reservations for retired adapters. If the NAS can connect through more than one port, decide whether each interface needs a unique address or whether the unused interface should remain disconnected.

Rebuild Address State Only After Fixing the Allocation Rule

After removing the overlap, clear stale leases for the two affected devices, renew their DHCP state, and flush the relevant client ARP or neighbor entry. Rebooting first may hide the symptom briefly without changing who is allowed to claim the address.

ZimaSpace’s guide to why home server addresses change provides the adjacent distinction between a normal DHCP address change and a true conflict caused by duplicate ownership.

Validate the repair with the startup order that used to trigger the problem: restart the router, allow it to finish, reconnect the competing device, then start the NAS. The conflict is fixed only when one MAC consistently receives or owns the reserved address and no second device can claim it after another restart.