MAC address vs IP address: What’s the difference?
MAC address vs IP address: One is a unique hardware identifier, while the other identifies a device's network connection. Learn more with BlueCat.
Read moreA dynamic IP address is an addressing method that assigns temporary addresses from a DHCP pool with a fixed lease duration, enabling organizations to efficiently support large numbers of client devices without manual per-device configuration. The DHCP process follows RFC 2131, where a server maintains a pool of addresses and tracks bindings with lease timers, allowing addresses to be reclaimed and reissued as devices connect and disconnect. Proper management of pool size, lease duration, and scope configuration is critical to prevent connectivity failures, conflicts, and security risks such as rogue servers and stale DNS records.
A dynamic IP address is normally assigned by a DHCP server, which hands out addresses from a configured pool and tracks each one as a lease with a fixed duration.
The exchange above follows the DHCP process defined in RFC 2131 for IPv4. Servers may reissue the same address to a returning client, so a dynamic address is not guaranteed to change. Administrators set lease length, pool ranges, and reservations to control how stable addresses are.
Clients fail to get an address and fall back to a link-local address in the 169.254.0.0/16 range. This often happens when a scope is sized for fewer devices than connect, or when long lease times keep addresses tied up by devices that have already left.
An unmanaged router or access point answers DHCP requests and gives clients the wrong gateway or DNS servers. Users report connectivity problems that affect only some devices, depending on which server answers first.
Two devices end up with the same address when a static address is configured inside a dynamic range, or when scopes on separate servers overlap. Symptoms include intermittent drops and duplicate address warnings on the affected hosts.
When a device changes address, its old A or PTR record can remain in DNS if dynamic updates fail or cleanup is not configured. Name lookups then return an address that now belongs to another device.
Clients on a remote subnet get no address because the router does not forward DHCP broadcasts to the server. The server logs show no requests from that segment, and the fix is a relay agent on the router interface.