Update IP

Perform a dynamic DNS update for a hostname or DDNS key

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string
required

A comma separated list of hostnames and groups to be updated. Hostnames may be of type A, AAAA, or Port 80 Redirect. The update response will be in the same order as this list.

Example: hostname=host1.example.com,group1,host2.example.com

If using DDNS Keys you may also set all.ddnskey.com as your hostname, this will update all hostnames attached to this DDNS key.

Hostnames may not always appear as a proper DNS name, for example group and special-use names.

string

The IP address to which the all hostnames in the update will be set to.

If no IP address is supplied, the client IP address connecting to our system will be used.

Clients behind NAT, for example, would not need to supply an IP address. If updating a dual-stacked DNS record (A and AAAA record for the same hostname), supply a comma separated list including your IPv4 and IPv6 address.

Example: 192.0.2.25,2001:0db8::2e

string

The IPv6 address to which the hostnames with AAAA records will be set.

Note: If myipv6 is supplied, this will override the IPv6 address in themyip field. This field is for compatibility with clients that do not allow IPv6 addresses in themyip field. The preferred method is to send the IPv6 address in themyip field.

string

Sets the current hostname to offline status.

Offline settings are an Enhanced / No-IP Plus feature. When offline mode is enabled, the hostname will use whatever offline method is selected on the No-IP.com website for that hostname.

Possible values are YES and NO with default of NO.

*If an update request is performed on an offline hostname, the hostname is removed from the offline state.

Example: NO

Headers
string
required

For hardware clients use the format:
User-Agent: Company DeviceName-Model/FirmwareVersionNumber

For software clients use the format:
User-Agent: Company NameOfProgram/OSVersion-ReleaseVersion

Sending a properly formatted User-Agent is important!

This helps us identify which type of update client software is sending updates to No-IP. It also allows us to provide better technical support to your end users.

Clients that are sending an update without a descriptive User-Agent risk being blocked.

string

The authorization header is available as an alternative to the Basic Auth method of authenticating.

Example: Authorization: Basic base64-encoded-auth-string

Response
200

Successful response

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here!