Dynamic DNS

Dynamic DNS keeps a record pointed at an address that changes, such as a home or branch connection. A router or a small script reports the new address to PrimeDNS, and the record follows the new address. It works with the DynDNS2 protocol that routers, ddclient and most update scripts already speak, and it is included in every plan.

1. Mark the record as dynamic

Only A and AAAA records can be dynamic. In the panel, open the zone, tick Dynamic DNS when you add the record or edit it. With the API, send "dynamic": true when you create the record or in a PATCH of it.

curl -X PATCH https://api.primedns.net/v1/dns/records/RECORD_ID \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"dynamic": true}'

Switching Dynamic DNS on lowers the TTL to the shortest one your plan allows, unless you send a TTL yourself. You can change the TTL afterwards like any other. The switch is recorded in the audit log.

2. Send an update

An update is an HTTPS request with HTTP Basic authentication:

curl -4 -u USERNAME "https://update.primedns.net/nic/update?hostname=home.example.com&myip=203.0.113.10"

USERNAME is the username of your PrimeDNS account, not its e-mail address. Curl asks for the password; routers and scripts store it with the other settings. hostname is the full name of the record. You can send several names separated by commas.

Parameters

ParameterMeaning
hostnameThe record to update, for example home.example.com.
myipThe new address. IPv4 updates the A record, IPv6 updates the AAAA record. Both can be sent as IPv4,IPv6. Optional: when it is missing, the address the request comes from is used.
myipv6An IPv6 address, sent next to an IPv4 myip. It replaces any IPv6 address given in myip.

IPv4 and IPv6

Without myip, the address of the connection is used. A computer with both IPv4 and IPv6 usually connects over IPv6, so only the AAAA record is updated, and a host that has only an A record answers nohost. Choose the family on purpose:

  • Force the connection: curl -4 ... for an A record, curl -6 ... for an AAAA record.
  • Or send the address yourself: myip=203.0.113.10, or myip=203.0.113.10&myipv6=2001:db8::10 to update both records at once.

Answers

The answer is a short text.

AnswerMeaning
good 203.0.113.10The record now has this address.
nochg 203.0.113.10The record already had this address. Nothing changed.
nohostNo dynamic record of this name and of the family of the address exists in your account. Check the name, that Dynamic DNS is ticked, and that you did not send an IPv6 address for a host that has only an A record.
badauth (HTTP 401)Wrong username or password. Use the username, not the e-mail address.
badipThe address is not a valid IPv4 or IPv6 address.
notfqdnThe host name is missing or not a full domain name.
abuseThe account cannot make changes at the moment, for example because its balance is not settled. See Restricted Mode.

Settings in routers and clients

Most devices have a DynDNS or Custom provider with these fields:

FieldValue
ProtocolDynDNS2 (dyndns2)
Serverupdate.primedns.net, HTTPS
UsernameYour PrimeDNS username
PasswordYour PrimeDNS password
Host nameThe full name of the dynamic record

For ddclient the same settings look like this:

protocol=dyndns2
use=web
server=update.primedns.net
ssl=yes
login=USERNAME
password='YOUR_PASSWORD'
home.example.com

Get a message when the address changes

Every real change of the address of a dynamic record sends the ddns.updated event. Add an endpoint for it and you are told each time the address changes, for example in a Slack, Discord, Microsoft Teams or Telegram channel, or on your own server. A request that repeats the current address sends nothing.

  1. In the panel, open Notifications and the Webhooks & chat tab, and add an endpoint. Chat services get a ready message.
  2. Choose the ddns.updated event for it. With the API, send "events": ["ddns.updated"] to POST /v1/webhooks.

Your own server receives the usual envelope, with the old and the new address in data:

{
  "id": "3f6c1e0a-7d8b-4b7e-9c1a-2f3e4d5c6b7a",
  "version": 1,
  "event": "ddns.updated",
  "account_id": 139111,
  "timestamp": "2026-10-22T10:15:30Z",
  "data": {
    "hostname": "home.example.com",
    "old_ip": "203.0.113.10",
    "new_ip": "203.0.113.25",
    "record": { "...": "the record after the change" }
  }
}

The message goes to an endpoint, not to e-mail, and the record changed alert rule leaves Dynamic DNS updates out on purpose, so it does not send one message for every update. How endpoints are set up and how to verify the signature of a delivery is in Webhooks & Alerts and Webhook events.

Check that it worked

The record in the panel shows the new address and a dynamic mark. The audit log shows each change of the address, made by Dynamic DNS, with the old and the new address. A request that repeats the current address is not logged.