Dynamic DNS (DynDNS2)

​

Set it up

curl -fsS -u "dnz:$DNZ_TOKEN" "https://dns.example.com/nic/update?hostname=home.example.com"

protocol=dyndns2
use=web
server=dns.example.com
ssl=yes
login=dnz
password=dnz_…
home.example.com

/tool fetch mode=https url="https://dns.example.com/nic/update?hostname=home.example.com" user=dnz password=dnz_… output=none

GET https://dns.example.com/nic/update?hostname=home.example.com&myip=203.0.113.7
Authorization: Basic base64("dnz:dnz_…")

​

How it behaves

• hostname takes one or more names, comma-separated, in zones the token can reach.
• myip takes IPv4 and/or IPv6 addresses, comma-separated. When empty, the caller’s address is used. Behind a reverse proxy, set DNZ_TRUSTED_PROXIES so that is the real address.
• The name’s A/AAAA records are replaced. New records get a TTL of 60.
• Names that have a CNAME are refused.
• The answer is one line per hostname: good <ip>, nochg <ip>, nohost, notfqdn, dnserr, badauth or 911.
• /api/ddns/update works as well as /nic/update.
• Only a zone’s default records are changed, never view records.