Dynamic does not mean constantly changing
Dynamic addresses are assigned automatically. In many IPv4 networks, DHCP supplies an address, a lease and other connection settings. Renewing a lease can keep the same address, and reconnecting may obtain it again. There is no universal rule that a dynamic address must change every few minutes or whenever a router restarts. The network's allocation policy determines how long it remains in use.
Be clear about which network
A static address is kept stable through an agreed assignment. It may refer to a device inside a local network or to the public address provided by an internet service. Manually entering a private address on a computer does not turn the household's internet exit into a static public IP. A router's DHCP reservation also provides local consistency; it is different from purchasing or arranging a fixed public address.
Where stability is useful
Stable addresses can help with managing equipment, hosting some services and maintaining address-based access rules. They do not automatically improve speed or security. Browsing, video calls and messaging generally work with dynamic addresses. Incoming access still depends on routing, firewalls and possible carrier-grade NAT. A fixed address alone is not proof that a service can accept connections from the wider internet.
Names can follow changing addresses
A domain can point to an address, and dynamic DNS can update that association as the address changes. It does not bypass every network restriction, and cached records may continue to reflect an earlier value until their lifetimes expire. Choose an addressing arrangement based on access needs, cost and the provider's terms. If you configure a local address manually, avoid conflicts with addresses already assigned to other devices.
DHCP reservation is not a static public IP
A router reservation repeatedly assigns the same local address to a device, useful for a printer or local server. Manually assigning a private address is also local configuration and requires avoiding conflicts. Neither fixes the public exit. External allowlists or a fixed public entry point require checking the provider’s public-address service and reachability.