Dynamic DNS


Dynamic DNS

Conexim supports Dynamic DNS (DDNS) using an open protocol widely adopted by most Dynamic DNS providers to facilitate the widest possible adoption by equipment vendors. Conexim enforces that Dynamic DNS updates are performed over a secure SSL connection to avoid eavesdropping of DDNS authentication information.

Old DDNS clients that cannot connect over HTTPS may not work with Conexim DDNS. Please contact Conexim Support to discuss your requirements if your device manufacturer cannot support SSL.

Dynamic DNS Configuration Generators

Conexim DNS can generate DDNS configuration information for the following platforms/software:

  • Cisco IOS® based routers.
  • Juniper JunOS® based routers.
  • ddclient for Linux, FreeBSD and other Unix-compatible operating systems.
  • A modified version of InaDyn that supports SSL (download from the download page of the Conexim Portal).

To use the configuration generation utility, simply select the type of client you wish to use from the dropdown in the DDNS section of Conexim DNS. This will include instructions and any additional information you may need to successfully configure DDNS.

DDNS Configuration

DDNS Configuration

DDNS Update Protocol

Some devices provide configurable Dynamic DNS support based on the provider’s protocol. The Conexim Dynamic DNS Update Protocol is as follows:


Conexim DNS also supports an alternative format:


In the above examples, the following items need to be set:

  • api_key_id: The API Key ID (DDNS Username). Not to be confused with the API Key itself.
  • ddnshostname.mydomain.tld: The fully qualified domain name of the record you wish to update. This record must exist as an “A” and/or “AAAA” record. If you wish to update multiple records at the same time, specify multiple fully qualified domain names separated by commas.
  • myip: The IP address to update the record with. If is specified, the incoming IP address is automatically detected and used as the update IP.

Important Note: Conexim DNS requires that requests specify a User-Agent header in all requests. This is used to help security mechanisms detect suspicious behaviour and is usually sent by default.

Unsupported Parameters

Similar Dynamic DNS protocols may support the following additional parameters. Conexim does not support the following. Passing these parameters will be silently ignored.

  • system
  • mx
  • wildcard
  • backupmx

Server Responses

The Conexim DDNS Update protocol will return one of the following:

Status Description
good Successful Dynamic DNS Update
nochg Record not changed as the existing record is the same.
nohost Unable to find the record to update. Please ensure you have the A or AAAA (if performing an update over IPv6) already configured.
badauth Bad Authentication – verify the authentication settings.
abuse Most likely the quota has been exceeded for the DNS Service. Please contact Conexim Support for further information.
badagent The request is malformed or not understood by the server.