Dynamic vs Static IP Addresses: What Actually Changes?

A dynamic IP address does not necessarily change every time a device connects. It is assigned through a mechanism and policy that may keep the same address for a long period. A static address represents a stable assignment policy. Neither term tells you whether the address is private or public.

Decide which address needs to stay stable

Keeping a printer at 192.168.1.40 does not fix the public address assigned by your Internet provider. Buying a static public IPv4 address does not automatically configure a fixed Wi-Fi address on a computer. Treat the local network and the Internet-facing connection separately.

A DHCP lease can retain the same address

DHCP leases an address and supplies other network information. A client can renew the lease or receive its previous address again after reconnecting. Restarting a router is therefore not a guaranteed way to change an IP address. Provider policy and access technology also affect the outcome.

On Windows, ipconfig /all can show DHCP and lease information for an interface. That describes the local interface; it does not establish how the provider allocates the public address. An address remaining unchanged for several days is not proof that the service contract includes static addressing.

Manual configuration and DHCP reservation

A local printer or server needing a stable address can use manual configuration or a DHCP reservation. With manual configuration, the address, prefix, gateway, and DNS settings are managed on the device. With a reservation, the client continues to use DHCP while the server assigns a reserved address to that client.

Do not choose an address merely because it looks unused. Check the DHCP pool, reservations, and network plan together. If the identifier used by a reservation changes, the expected assignment may fail. Private or randomized MAC settings on some devices are relevant when investigating that behaviour.

Remote access needs more than a static address

A stable public address can simplify DNS and allowlists. Dynamic DNS can track a changing public address, but it does not remove CGNAT or inbound filtering. Port forwarding cannot automatically bypass restrictions upstream at the provider.

Do not assume that exposing a camera or administration panel directly to the Internet is the required solution. An authorized VPN or a controlled access service may fit better. Authentication, updates, and access restrictions remain separate requirements with any approach.

Dynamic addressing is not a security control

A changing address is not automatically safe, and a fixed one is not inherently unsafe. Exposed services, weak credentials, and incorrect firewall rules create risks in either case. Pricing and whether a static-address service removes CGNAT depend on the provider's terms.

Record the current configuration before editing it and arrange a recovery path, especially over a remote connection. Describe the requirement precisely: stable local access, a fixed public exit, or accepting inbound connections. Those are different problems. Protocol reference: DHCP.