Reference
API Reference
NovaDNS exposes two update endpoints: a native token-based API and a DynDNS-compatible endpoint for legacy clients and firmware.
Authentication
Two authentication methods are supported. Both are equivalent in capability.
Recommended
token query parameter. Each host has its own token, rotatable from the dashboard at any time.Legacy compat
Endpoints
/api/updateNative token-based endpoint. Detects your public IP automatically from the incoming request. Optionally accepts an explicit IP via the myip parameter.
$ curl "https://novadns.io/api/update?token=YOUR_TOKEN"
/nic/updateDynDNS-compatible endpoint. Accepts Basic Auth (host username:password) and the standard hostname and myip query parameters. Returns a DynDNS-style response string.
$ curl \ "https://YOUR_HOST_USERNAME:YOUR_HOST_PASSWORD@novadns.io/nic/update \ ?hostname=home.novaip.link&myip=203.0.113.42"
Parameters
tokenyesYour 64-character host update token. Required for /api/update.hostnamenoThe full hostname to update (e.g. home.novaip.link). Required for /nic/update.myipnoExplicit IP address or CIDR prefix (IPv4 or IPv6). Auto-detected from request if omitted.Responses
The native endpoint returns JSON. The DynDNS endpoint returns a plain-text string.
{ "ipv4": "203.0.113.42", "ipv6": "2001:db8::1" }
good 203.0.113.42If only IPv4 is detected, ipv6 is null. If only IPv6 is detected, ipv4 is null.
Error codes
Was this page helpful?