Configure Dynamic DNS to map a domain to your changing home IP

Quick answer

You want to reach your home network from outside — a game server, a NAS, a security camera, remote desktop — but your home IP keeps changing, so you can’t just memorise it. Dynamic DNS (DDNS) solves this by giving you a hostname that always points at your current IP.

What problem does Dynamic DNS solve?

Most home connections use a dynamic IP that changes periodically. Anything you set up to reach your home — a bookmarked address, a port-forwarded service — breaks when the IP rotates. A static IP would fix it but costs extra. DDNS is the free workaround: a hostname like myhome.ddns.net that automatically updates to track your changing IP.

How it works

A small DDNS client — running on your router or a device at home — watches your public IP and, whenever it changes, tells the DDNS provider the new address. The provider updates the hostname’s DNS record to match. So myhome.ddns.net always resolves to wherever your home IP currently is, even as the underlying address shifts.

Step 1: Pick a DDNS provider

Many routers have DDNS built in and list supported providers in their settings (No-IP, DuckDNS, Dynu, and others offer free tiers). Choose one your router supports if possible — that’s the simplest setup. Otherwise, run the provider’s small update client on an always-on home device.

Step 2: Configure the updater

Create a hostname with the provider, then enter its credentials into your router’s DDNS section (or the client). The updater now keeps that hostname pointed at your live IP automatically. From then on, you use the hostname instead of the IP for everything.

Step 3: Port-forward and test

DDNS only handles the address — you still need to port-forward the service to the right internal device. Once both are set, connect using hostname:port from outside your network to confirm it works. Test from mobile data or a friend’s connection, not from inside your own LAN.

The CGNAT caveat

DDNS can’t help if you’re behind carrier-grade NAT — the hostname would point at a shared carrier address that can’t accept inbound connections to you. If port forwarding never works no matter what, check whether you’re on CGNAT (common with mobile and some fibre ISPs); the fix is a public IP from your ISP or a tunnelling service.