From db8b6baca9f86bf4be53332bb953be7fc7d1b109 Mon Sep 17 00:00:00 2001 From: Krerkkiat Chusap Date: Mon, 5 Apr 2021 12:36:45 -0400 Subject: [PATCH] modify Cloudflare documentation It seems that ddclient check if the login field is equal to "token" to use the correct header for the API token. --- ddclient.conf.in | 2 +- ddclient.in | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/ddclient.conf.in b/ddclient.conf.in index 164a260..b36b514 100644 --- a/ddclient.conf.in +++ b/ddclient.conf.in @@ -192,7 +192,7 @@ ssl=yes # use ssl-support. Works with #protocol=cloudflare, \ #zone=domain.tld, \ #ttl=1, \ -#login=your-login-email, \ # Only needed if you are using your global API key. +#login=your-login-email, \ # Only needed if you are using your global API key. If you are using an API token, set it to "token" (wihtout double quotes). #password=APIKey \ # This is either your global API key, or an API token. If you are using an API token, it must have the permissions "Zone - DNS - Edit" and "Zone - Zone - Read". The Zone resources must be "Include - All zones". #domain.tld,my.domain.tld diff --git a/ddclient.in b/ddclient.in index 4ddd505..1b9e3a9 100755 --- a/ddclient.in +++ b/ddclient.in @@ -4733,6 +4733,7 @@ Example ${program}.conf file entries: ## single host update using an API token protocol=cloudflare, \\ zone=dns.zone, \\ + login=token, \\ password=cloudflare-api-token \\ myhost.com