Parameter

combination are missing, the update with the badauth return code will fail.

• An existing Authorization header may overwrite username/password combinations passed as parameters. }}

---

Securepoint Dynamic DNS Parameter

Last adaption: 08.2022

New:

• Layout adjustment

notempty

This article refers to a Resellerpreview

2017

Access: https://update.spdyn.de/nic/update

---

Syntax:	https://update.spdyn.de/nic/update?hostname=Domain&myip=IPv4Address,IPv6Address&user=Username&pass=Password
Example	https://update.spdyn.de/nic/update?hostname=ttt-point.spdns.eu&myip=203.0.113.113,2001:db8::db8&user=ttt-point.spdns.de&pass=1234567-abcd-efgh-ijkl
Parameter-Name	Example	Explanation
hostname	ttt-point.spdns.de or ttt-point.spdns.de,ttt-point.spdns.eu	A single FQDN or a comma separated list (max 20 entries) of FQDNs to be updated When updating via tokens, a comma-separated list cannot be used because each token only matches exactly one host
myip	203.0.113.113 or 2001:db8::db8 or 203.0.113.113,2001:db8::db8	Exactly one IPv4 address and/or exactly one IPv6 address with which the hosts are to be updated. If both IP versions are updated, the IP addresses must be separated by a comma. If the IP passed in the myip parameter is in a private subnet (10.0.0.0/8, 172.16.0.0/20, or 192.168.0.0/16), the update script will use the public IP used to establish the connection to update instead. This behavior is only enabled if both the myip parameter and the client IP of the HTTP connection is an IPv4 address.
user	spdynUser1 or ttt-point.spdns.de	The name of a user who can update this host. If token Update token is used, the host name is also entered here. The user and pass parameters are to be used only if no HTTP Basic-Auth is performed. If both the Authorization header and the user/{code
pass	secretP4ssw0rd or 1234567-abcd-efgh-ijkl	The password of a user who can update this host. If Update token is used, this is what is entered here. secretP4ssw0rd is an example and should under no circumstances be used!