Documentation

Quickstart

1. Create an account (free, one hostname).
2. In the dashboard, create a hostname like yourname.wanderip.com.
3. Generate an API token (recommended) or use your account password.
4. Configure your router or DDNS client to send updates to update.wanderip.com using the dyndns2 protocol.
5. That's it. Your hostname now follows your IP wherever it wanders.

Protocol

WanderIP speaks dyndns2, the de-facto standard supported by virtually every router and DDNS client. To update a hostname, send an HTTP GET request with HTTP Basic Authentication:

GET https://update.wanderip.com/nic/update?hostname=HOSTNAME&myip=IP
Authorization: Basic base64(username:password-or-token)

The myip parameter is optional. If omitted, WanderIP uses the source IP of the request, which is what you want in most cases.

You can also send IPv6 with myipv6=..., and combine both in one request.

Example with curl:

curl -u USERNAME:TOKEN \
  "https://update.wanderip.com/nic/update?hostname=yourname.wanderip.com"

Router setup

Most routers have a built-in Dynamic DNS section under WAN, Network, or Services. Pick "Custom" provider (or "dyndns2" if available), and use these settings:

pfSense / OPNsense

1. Services → Dynamic DNS
2. Add a new entry, set Service Type to Custom
3. Interface: your WAN interface
4. Update URL: https://update.wanderip.com/nic/update?hostname=%h
5. Hostname: yourname.wanderip.com
6. Username and Password: as above
7. Save. Click Force Update to test.

ASUS / AsusWRT-Merlin

1. WAN → DDNS
2. Enable: Yes
3. Server: Custom
4. Hostname: yourname.wanderip.com
5. Username, Password: as above
6. If using Merlin: edit /jffs/scripts/ddns-start to call update.wanderip.com directly.

Ubiquiti UniFi / EdgeRouter

1. Network → System Settings → Dynamic DNS (or via SSH on EdgeRouter)
2. Service: custom (dyndns2)
3. Server: update.wanderip.com
4. Hostname, Username, Password: as above

Synology DSM

1. Control Panel → External Access → DDNS → Add
2. If WanderIP isn't in the provider list, click Customize Provider Name
3. Provider: WanderIP (any name; pick "dyndns" if asked for protocol)
4. Query URL: https://update.wanderip.com/nic/update?hostname=__HOSTNAME__&myip=__MYIP__
5. Hostname, Username, Password: as above

ddclient (Linux)

The reference dyndns2 client. Install on Debian/Ubuntu: sudo apt install ddclient. Then edit /etc/ddclient.conf:

protocol=dyndns2
use=web, web=checkip.amazonaws.com, web-skip='Current IP Address:'
server=update.wanderip.com
ssl=yes
login=YOUR_USERNAME
password='YOUR_TOKEN'
yourname.wanderip.com

Restart: sudo systemctl restart ddclient. Logs: journalctl -u ddclient -f.

Response codes

All responses are plain text. WanderIP follows the dyndns2 spec:

Troubleshooting

Updates fail with badauth

Most likely your username or token is wrong. Double-check capitalization. Tokens start with wip_. If using a password and you recently changed it, your router still has the old one.

Updates fail with nohost

The hostname doesn't exist in your account. Create it in the dashboard first. Also check spelling; my-server is not the same as myserver.

Updates fail with abuse

Your router is sending updates too often. Most routers should only update on IP change; if yours is hitting us every minute, check its configuration. WanderIP requires at least 60 seconds between updates.

DNS doesn't resolve to my new IP

Check the dashboard to confirm the update went through. If it shows the right IP but dig still returns the old one, DNS resolvers may be caching. Wait up to your TTL (default 60 seconds) or test against ours directly: dig @ns1.wanderip.com yourname.wanderip.com.

API tokens

Tokens are revocable credentials you can put in your router instead of your account password. Benefits:

• If a router is compromised or replaced, revoke the token without changing your account password.
• Per-device tracking: see when each token was last used.
• If you change your password, tokens keep working.

Create one in the API tokens page. Tokens are shown only once at creation; copy and store them then. They look like:

wip_aBc123...

Use the token as the password in your router config, with your account username as the username.