legitdns docs
Documentation for legitdns, the dynamic DNS service.
Start here
- Getting started - sign up, claim a hostname, send your first update.
- Reaching your device from outside - port forwards, double NAT, and shared provider addresses (CGNAT): why a working hostname is not always a reachable device.
- Moving from another DDNS provider - switching from No-IP, Dyn, or Duck DNS, and running both during the move.
- Tokens - the per-hostname update token: where it lives, how to replace it, how to protect it.
Updating your hostname
- Update methods - the four ways to send an update, and which fits your setup.
- Client guides - our scripts, ddclient, inadyn, and curl, with configs we tested ourselves.
- legitdns on Windows - a PowerShell scheduled updater, and the Windows clients that can point at a custom server.
- legitdns on macOS - a script macOS runs by itself on a schedule, the Homebrew client, and a GUI option.
- Router guides - built-in DynDNS settings on routers, router firmware, and NAS systems, per brand.
- Panel guide - hostnames, tokens, TTL, offline, wildcard, redirect, SRV records, certificates, referrals, two-factor.
- IPv6 prefix mode - when your provider rotates the first half of your IPv6 address.
Reference
- Update API - the
/api/v1/updateendpoint and the/checkiphelper. - DynDNS2 protocol - the
/nic/updateendpoint routers and DDNS clients speak, with every answer code. - Troubleshooting and FAQ - fixes keyed to the answer codes.
Examples use sample names like mypi.pihome.example; the panel shows the real domains when you claim a hostname. A client or router is only called "supported" here after we have tested it against the service ourselves.