Add No-IP
If your device already has a Dynamic DNS update client, Basic Integration is EASY!
Industry Standard Protocol
Raw HTTP GET Request
GET
/nic/update?hostname=mytest.example.com&myip=192.0.2.25 HTTP/1.1
Host: members.ddnsprovider.org
Authorization: Basic base-64-authorization
User-Agent: Company Model / Version
name@domain.com
Example update request string
http://username:password@members.ddnsprovider.org/nic/update?hostname=mytest.example.com&myip=192.0.2.25
No-IP Protocol
Raw HTTP GET Request
GET
/nic/update?hostname=mytestyourhost.example.com&myip=192.0.2.25
HTTP/1.1
Host: dynupdate.no-ip.com
Authorization: Basic base-64-authorization
User-Agent: ##SEE SETTING the User-Agent Below##
Example update request string
http://username:password@dynupdate.no-ip.com/nic/update?hostname=mytest.example.com&myip=192.0.2.25
Please Note: Any additional parameters (ie wildcard, mx, backmx, etc;) will be ignored by No-IP update servers.
Important: Setting the Agent
When making an update it is important that your http request include an HTTP User-Agent to help No-IP identify different clients that access the system. Clients that do not supply a certified and approved User-Agent risk being rate-limited or blocked from the system. Please use the following User-Agent generator to obtain a certified and approved User-Agent.
For hardware clients use the format:
User-Agent: Company DeviceName-Model/FirmwareVersionNumber maintainer-contact@example.comFor software clients use the format:
User-Agent: Company NameOfProgram/OSVersion-ReleaseVersion maintainer-contact@example.comUser Agent is important! It helps us identify what Update Client is accessing us. This allows us to provide better technical support to YOUR USERS.