Router guides

If your router can update a custom DDNS service, it can keep your legitdns hostname current by itself - no Pi or script needed. This page collects the routers, router software, and NAS systems whose makers document a custom update URL or custom server option.

Read this first: none of these has been tested against legitdns yet. Every entry below is "should work - not yet verified by us": the maker's own manual documents the feature, but we have not run that model against the service. Only the client guides are tested, and only those are called supported. If you try one of these, your history page (see troubleshooting) tells you whether it worked.

The values every setup needs

Whatever the brand, the pieces are the same:

• Service type: custom / user-defined DynDNS (the protocol is DynDNS2).
• 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).
• The router fills in the address itself; where a guide shows a placeholder for it, that is the maker's own syntax, given where the maker documents one.

Routers

FRITZ!Box

FRITZ!OS has a user-defined provider option with an update URL - the best-documented custom setup of any consumer router.

1. Open the FRITZ!Box Dynamic DNS settings.
2. Provider: User-defined.
3. Update URL: https://<username>:<pass>@legitdns.com/nic/update?system=dyndns&hostname=<domain>&myip=<ipaddr>&myipv6=<ip6addr> (those angle-bracket words are FRITZ!Box's own placeholders - type them exactly as shown).
4. Domain name: your full hostname. Username: the hostname again. Password: the token.
5. Check History in your panel to confirm updates are arriving.

Peplink (B One and similar)

The manual documents an "Others..." DDNS choice for custom DynDNS-compatible servers, by URL.

1. Open the DDNS settings for your WAN connection.
2. Service: Others...
3. Enter the update URL from the box above, with your hostname as the username and the token as the password where it asks.
4. Check History in your panel to confirm updates are arriving.

Teltonika (RUT series)

RutOS has a provider list plus a custom option; Teltonika's own examples build the custom URL in exactly the DynDNS2 form.

1. Open Services > Dynamic DNS.
2. Provider: -- custom --.
3. Custom update URL: https://[username]:[password]@legitdns.com/nic/update?hostname=[domain]&myip=[IP address] (Teltonika's placeholder style, from its own examples).
4. Username: your hostname. Password: the token.
5. Check History in your panel to confirm updates are arriving.

TP-Link Omada gateways (ER605 and similar)

The Omada business line. Consumer Archer and Deco models are different - see the end of this page.

1. Open the Custom DDNS settings (standalone or controller mode both work).
2. Update-URL: https://[USERNAME]:[PASSWORD]@legitdns.com/nic/update?hostname=[DOMAIN]&myip=[IP] (Omada's placeholders, from its FAQ).
3. Username: your hostname. Password: the token.
4. Set the update interval to a custom value rather than Fixed mode - Fixed mode's shortest interval is one hour.
5. Check History in your panel to confirm updates are arriving.

Router software and firmware

OpenWrt (ddns-scripts)

OpenWrt's DDNS package takes a custom update URL natively, in LuCI or in the config file.

Config file (/etc/config/ddns):

config service 'legitdns'
    option enabled '1'
    option service_name '-'
    option update_url 'https://[USERNAME]:[PASSWORD]@legitdns.com/nic/update?hostname=[DOMAIN]&myip=[IP]'
    option username 'mypi.pihome.example'
    option password 'YOUR-TOKEN'
    option domain 'mypi.pihome.example'
    option interface 'wan'
    option ip_source 'network'
    option ip_network 'wan'

(The bracketed words are ddns-scripts' own placeholders.) HTTPS needs a TLS-capable download tool on the router - if updates fail with SSL errors, install curl or wget-ssl.

The same ddns-scripts ship across the OpenWrt family - Turris OS, ImmortalWrt, ROOter / GoldenOrb, X-WRT, LibreCMC, and OpenMPTCProuter inherit this setup. Gargoyle has its own DDNS client instead: add a service entry with a url_template to /etc/ddns_providers.conf, in the /nic/update form used above. All of these are "should work" like the rest of this page.

Whichever of these you run: check History in your panel to confirm updates are arriving.

FreshTomato (and Tomato64)

1. Open Basic > DDNS.
2. Service: Custom URL.
3. Enter the update URL with your credentials in it, in this form: https://mypi.pihome.example:[email protected]/nic/update?hostname=mypi.pihome.example FreshTomato's wiki documents how its Custom URL option adds the current address - check it against your build.
4. Check History in your panel to confirm updates are arriving.

Tomato64 inherits FreshTomato's DDNS page; same steps.

pfSense

1. Open Services > Dynamic DNS.
2. Add a client with Service Type Custom.
3. Enter the update URL from the box above and your hostname and token in the username and password fields.
4. Check History in your panel to confirm updates are arriving.

OPNsense

The os-ddclient plugin's native backend supports custom HTTP requests for unlisted services. The manual documents the capability but not per-field steps, so treat this as "the option exists": add a custom account, point it at the update URL above with your hostname and token. Then check History in your panel to confirm updates are arriving.

VyOS

VyOS speaks dyndns2 natively with a custom server - no free-form URL, the protocol path is standard. Configure the dynamic DNS service with protocol dyndns2, server legitdns.com, host-name set to your hostname, username your hostname, password its token. Then check History in your panel to confirm updates are arriving.

Ubiquiti EdgeOS (EdgeRouter)

From the CLI, define a custom dynamic DNS service under service dns dynamic for your WAN interface: server legitdns.com, the DynDNS2 protocol, login your hostname, password its token. Then check History in your panel to confirm updates are arriving.

Asuswrt-Merlin (scripting)

Stock ASUS firmware cannot do this (see the list below), but the Asuswrt-Merlin fork can, through its custom DDNS script hook:

1. In the DDNS settings, set the service to Custom, and enable custom scripts.
2. Create /jffs/scripts/ddns-start:

#!/bin/sh
# $1 is the WAN address Merlin hands the script
if curl -s -u "mypi.pihome.example:YOUR-TOKEN" \
  "https://legitdns.com/nic/update?hostname=mypi.pihome.example&myip=$1" \
  | grep -q "^good"; then
    /sbin/ddns_custom_updated 1
else
    /sbin/ddns_custom_updated 0
fi

1. Make it executable: chmod +x /jffs/scripts/ddns-start.
2. Check History in your panel to confirm updates are arriving.

MikroTik RouterOS (scripting)

RouterOS's built-in DDNS is MikroTik's own cloud only, but /tool fetch can call any update URL, so a small script plus a scheduler entry does the job:

# a script that publishes the address IP Cloud reports
:local ip [/ip cloud get public-address]
/tool fetch mode=https http-method=get \
  url="https://legitdns.com/nic/update?hostname=mypi.pihome.example&myip=$ip" \
  user="mypi.pihome.example" password=<redacted> keep-result=no

Run it every few minutes from the scheduler. Treat it as a starting point to adapt - and check History in your panel to confirm updates are arriving.

NAS systems

A NAS that is always on can do this job itself. Both systems below are "should work - not yet verified" like the rest of this page.

Synology DSM

DSM's DDNS page has a Customize Provider option; Synology's manual documents the form and the placeholders it fills into your update URL.

1. Open Control Panel > External Access > DDNS.
2. Click Customize Provider. Service Provider: legitdns. Query URL: https://__USERNAME__:[email protected]/nic/update?hostname=__HOSTNAME__&myip=__MYIP__ (the double-underscore words are DSM's own placeholders - type them exactly as shown).
3. Click Add and pick legitdns in the Service Provider list (custom providers show with an asterisk). Hostname: your full hostname. Username: the hostname again. Password/Key: the token. External Address: Auto.
4. Check History in your panel to confirm updates are arriving.

QNAP QTS

QNAP's manual documents the DDNS screen and its fields - but read step 3 before you start: it documents a provider list, not a custom update URL.

1. Open Control Panel > Network & File Services > Network & Virtual Switch, then Access Services > DDNS, and click Add.
2. The fields are: Select DDNS server (the provider), Username, Password, Hostname, and Check the External IP Address (how often it checks).
3. legitdns is not in QNAP's provider list, and the manual shows no custom-URL field for this screen - so from the documented options alone, this screen cannot be pointed at legitdns. QNAP's spec sheets describe the DDNS settings as customizable; if your build's server list has a custom or user-defined entry, it needs the update URL and values from the box at the top of this page. If it does, check History in your panel to confirm updates are arriving.
4. Otherwise, run an updater on a device inside the network instead - a Pi with our script is the standard answer.

These cannot use legitdns yet

These makers lock the DDNS client to a built-in provider list, with no custom option in their documentation. There is no setting to find; the fix is the maker adding one.

• TP-Link Archer (consumer line) and TP-Link Deco
• ASUS routers on stock Asuswrt (ASUS's own FAQ says custom DDNS services are not supported)
• Netgear Nighthawk / Orbi
• Linksys (the legacy lines we could document)
• GL.iNet routers in the stock panel (their own DDNS only; the OpenWrt layer underneath is a different, undocumented-by-GL.iNet route)
• Zyxel's service-provider line
• IPFire (its provider list has no custom entry; a legitdns provider would have to be added to IPFire's own client)

Behind one of these, run an updater on a device inside the network instead - a Pi with our script is the standard answer.

Not yet checked either way

We could not settle these from the makers' own documentation, so they are unlisted rather than guessed at: UniFi gateways (the manual hints at an optional server field - the most promising lead here, and first in line for a live test), DD-WRT, Synology SRM (their router system - DSM, on the NAS boxes, is covered under NAS systems above), D-Link, Linksys Velop, other Zyxel lines, and Padavan. If you run one and its DDNS page offers a custom URL or server, enter the values from the box at the top; your history page tells you if it worked.