How it works

Pending

the change is recorded, not yet published

Applied

the primary server publishes the new address

Served

ns1, ns2 and ns3 publish the address

No address

no A or AAAA record

Suspended

removed from the zone by the administration

Error

publishing failed; it is retried automatically

A DynDNS2 update replies good once the primary server publishes the address, usually within one or two seconds. The three public servers receive it a few seconds later. Records have a 60-second TTL: a resolver that kept the old address usually replaces it within a minute.

The two families are independent. Without a myip parameter, only the connection’s family changes: a request arriving over IPv4 leaves the IPv6 address alone. api4.nomadns.net and api6.nomadns.net let a client update each family separately.

The zone is served by ns1, ns2 and ns3, at two different hosting providers. It is signed with DNSSEC. Each token works for one subdomain and one use; its secret is never stored in clear.

To change several addresses at once, the zone file editor (link on the subdomain page) accepts A and AAAA records for the account’s subdomains, in DNS format. It previews additions, changes and removals before applying them.

120 requests per hour per subdomain, 60 address changes per day per subdomain, 10 authentication failures per 10 minutes per IP address. Beyond that, the reply is abuse or badauth until the end of the window. Rotating a token does not reset these limits. Web edits and zone imports count toward the daily DynDNS budget and always remain available.

Sign-in to your account: 10 failures per 10 minutes per IP address, 20 per hour per account. Beyond that, sign-in is refused until the end of the window, even with the right password.