Moving from another DDNS provider

Coming from No-IP, Dyn, Duck DNS, or another provider: you claim a new hostname here and point your updater at it. Nothing transfers automatically, and your old name stays yours at the old provider until you close it there - so you can move in stages, with both running.

How your old setup maps to this one

What you had	Here
Your old hostname (like you.no-ip.com)	A hostname you claim under one of our domains
The provider picked in your router or client	The custom / DynDNS2 values below
Your old update username and password	Username: your full legitdns hostname. Password: that hostname's update token - not your account password
Duck DNS's one token for the whole account	One token per hostname here - narrower on purpose: a leaked token touches one hostname, nothing else

The values every DynDNS2 setup needs:

• Server: legitdns.com
• Update URL: https://legitdns.com/nic/update?hostname=<hostname>&myip=<ip>
• Username: your full hostname, e.g. mypi.pihome.example
• Password: that hostname's update token (see Tokens).

If your router's DDNS page only lists providers, with no custom option, it cannot talk to us - run our script on a device inside the network instead. The router guides say which routers have the custom option.

The habit you can drop

No-IP's free names need confirming every 30 days or they stop working. There is no monthly check-in here and no confirmation link to click. The only clock is account inactivity: if your account has no activity for six months - no sign-in, no updates - we send warning emails first (about a month before, and again about a week before), then withdraw your hostnames so they stop resolving, and the account may then be closed and its hostnames freed for others to register.

Run both during the move

1. Claim your legitdns hostname and set up its updater (a client, a router custom entry, or the API).
2. Leave the old updater running for the old name. Two services side by side is fine: what matters is one updater per hostname, and that is about the name, not your network.
3. Move the things that use the name - bookmarks, app settings, other people - to the new name.
4. Confirm the move: check History in your panel for updates arriving, and dig +short your-new-hostname.

When to remove the old client

Once the new name resolves and everything you use points at it, turn the old updater off. Leaving it on does us no harm - it only updates the old provider - but two names for one device drift apart in your bookmarks. Close the old account too if you are done with it.

Next: Getting started if this is your first hostname here.