I worked around it by using the web interface to make the service also "custom" like Google, and specified their server manually as members.
This resulted in a correct config and works around the issue for me.
Dots, dashes, and underscores allowed, but not at the beginning or end of the string.
Users will also enter a list of hostnames (FQDNs) to be updated.
Clients can determine the current public IP via the operating system's network stack or via web detection, useful for private IPs (RFC 1918 space). Implementors MUST NOT hard code the IP for updates.as they may change from time to time.
On dirait que cela vient du charactre & dans l'url GET mais je ne vois pas en quoi cela gne ?My ER-Po E had been updating a hostname on for several years, and is currently running 1.9.7.Today, I tried to add a second hostname through the web interface, this one hosted on Google domains (which likewise uses the dyndns2 protocol). My issue is that adding the # # autogenerated by on Wed Jul 26 PDT 2017 # daemon=1m syslog=yes ssl=yes pid=/var/run/ddclient/ddclient_eth1cache=/var/cache/ddclient/ddclient_eth1.cache use=if, if=eth1 server=domains.google.com,protocol=dyndns2 max-interval=28d login=[redacted] password=[redacted] [google-hosted domain redacted] protocol=dyndns2 max-interval=28d login=[redacted] password=[redacted] [dyndns-hosted domain redacted] That second clause is supposed to be the service, but it's missing the "server" key.Your client should instead notify the user of the problem have them attempt to correct it before trying again.If the error return code requires No-IP intervention your client should tell the user to contact our support team.
See the status code descriptions for return codes that require contacting No-IP Support.