One week your public IP ends in .42, the next it ends in .97. Nothing is broken and nobody is attacking you - that is how home internet is designed. Here is what the two kinds of address really are, why yours keeps moving, and the simple trick that makes the movement irrelevant to your website.
Every home-hosting plan starts with a small shock: the address you are supposed to publish to the world is not yours to keep. The video this guide accompanies solves that with Dynamic DNS, but it helps to understand what is actually changing and why - because once you see it, you will also see exactly which problems a static IP would solve, and which ones it would not.
When your router connects, the ISP hands it an address from a shared pool - a system called DHCP. The address comes with a lease, like a library book. When the lease is renewed you usually keep the same address, but a router restart, ISP maintenance or a pool reshuffle can hand you a different one. Leaving the router off overnight is the classic way to wake up with a new IP.
This is normal, healthy and true for almost every home connection on earth. The address is a temporary loan, and your hosting plan must be built for a loan - not pretend it is a purchase.
A static IP is the same pool, with one address pinned to your connection forever. It is normally a paid business add-on. It buys exactly one thing: findability - other machines can hard-code your address and always reach you.
That matters for a few jobs: an office firewall that only trusts one home address, a mail server (which needs a fixed, reputable address), some VPN and camera setups. For a website, findability is a real need - but it is a need a name can meet just as well as a number, which is the whole point of the next cards.
Two honest reasons. First, IPv4 addresses ran out years ago; rotating a smaller pool across many customers is how ISPs stretch them. Second, a fixed address is a product: keeping home addresses dynamic lets the ISP sell static ones to businesses. Your changing IP is partly engineering and partly a price list. Neither reason is going away, so build for the world as it is.
Either way, the public face of the site - the domain - never changes. The machinery underneath absorbs the movement.
Be honest about the short list. Pay for static when an office firewall must whitelist your home, when you run a mail server, or when some equipment you depend on demands a fixed address and has no name-based option. A portfolio website, a family site, a learning project - none of these are on the list. For them, the paid add-on buys convenience you can get free from Dynamic DNS in about ten minutes of setup.
Watch the video to see the Dynamic DNS route set up live, so a normal changing home connection hosts a stable website.
▶️ Watch Full VideoIt varies too much to promise: some connections keep one address for months, others change it daily or at every router restart. Reconnects and ISP maintenance are the usual triggers. That unpredictability is exactly why the update must be automatic - no human routine survives it.
No. Speed, latency and security are identical - only findability differs. And a changing address is not a security feature either: scanners sweep whole address ranges constantly, so a fresh IP is found just as fast as an old one.
Usually yes, as a paid add-on - many ISPs will enable one on request. For website hosting alone, Dynamic DNS gives the same practical result for free. Pay for static when something on your list, like firewall whitelisting or a mail server, truly requires the number itself to never move.