Host Your Website From Home Without a Static IP Complete Setup Guide

A website needs one thing above all: an address visitors can always find. A static IP gives you that by never changing. A normal home connection gives you a dynamic IP - it changes when the router reconnects or the ISP rotates its pool, sometimes every few days.

The video's whole idea is one honest trick: do not fix the address, fix the directions. A Dynamic DNS hostname is a name whose record is rewritten automatically every time your address changes. Visitors use the name; the name always points at today's address. Everything else in this guide is plumbing around that one idea.

In the video, Anshu deliberately plays a complete beginner and builds the website with AI help inside Trae IDE - proof that the building part no longer needs deep coding knowledge. For hosting, it genuinely does not matter what built the site.

1. A plain HTML website is the easiest tenant: fast, tiny, and almost nothing to patch.
2. A heavier site (WordPress class) also works, but it brings a database and a steady stream of updates you must keep up with.
3. Finish and test the site on the PC itself before you touch the router. Hosting steps are identical for every kind of site - only the serving software changes.

The PC becomes a server by running web server software. Pick the lightest one that fits your site:

1. Plain HTML site: a small static file server, or IIS - the web server built into Windows - is plenty.
2. PHP or WordPress site: an all-in-one stack of the XAMPP class (web server, PHP and database in one install).
3. Open http://localhost in the PC's own browser. The site must load here first. If it fails locally, it will fail for the world too.
4. Set the server to start automatically with Windows, so a reboot never leaves the site down.
5. Now fix the PC's local address: in the router, reserve an address for this PC (DHCP reservation), or set a static local IP on the PC. Port forwarding points at a local address - if that address drifts to another device, the site dies even though the internet side is perfect. Check the current local address any time with ipconfig.

Open the router admin page (commonly 192.168.0.1 or 192.168.1.1), find Port Forwarding, and create exactly two rules, both aimed at the PC's reserved local address:

1. External port 80 to PC port 80 - normal web traffic (HTTP).
2. External port 443 to PC port 443 - secure web traffic (HTTPS).

That is the complete door list for a website. Nothing else needs forwarding, and every extra open port is extra risk with no benefit.

Create a free Dynamic DNS hostname (a name under a DDNS provider's domain - the video sets one up step by step). Then tell something in your home to keep its record true:

1. Best place: the router itself. Most routers have a Dynamic DNS page - enter the hostname and your DDNS account once, and the router updates the record the moment its WAN address changes. It runs day and night and sees the change first.
2. Fallback: an updater program on the PC. Works fine, but the PC must be on for updates to happen - acceptable, since the PC is your server anyway.
3. Prove it works: note your public IP, restart the router, wait for a new IP, then run nslookup yourname.example-dns.com (an example hostname) - the answer should become the new address within minutes.

A DDNS hostname works, but your own domain looks professional and stays yours forever. At your domain registrar:

1. Add a CNAME record for www pointing to your DDNS hostname. The domain now follows wherever the DDNS record points - the IP can change daily and the domain never notices.
2. For the bare root domain, most registrars offer an ALIAS/ANAME record or a simple redirect to the www address.
3. Allow time for DNS to spread - minutes to a few hours depending on TTL. Test from your phone with Wi-Fi off.