From ae7919fcc43b9d858b78f21ba46da72fc369c1c0 Mon Sep 17 00:00:00 2001 From: Richard Hansen Date: Sat, 18 Jul 2020 15:04:18 -0400 Subject: [PATCH] Mark `gandi` protocol's `ttl` var as optional Gandi doesn't require a TTL in the update request. The protocol implementation already does the right thing if the `ttl` var is `undef`. --- ddclient.in | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/ddclient.in b/ddclient.in index 65551e9..fe287d6 100755 --- a/ddclient.in +++ b/ddclient.in @@ -580,7 +580,7 @@ my %services = ( 'min-interval' => setv(T_DELAY, 0, 0, 0, interval('5m')), 'server' => setv(T_FQDNP, 1, 0, 'api.gandi.net', undef), 'script' => setv(T_STRING, 1, 1, '/v5', undef), - 'ttl' => setv(T_DELAY, 1, 0, interval('3h'), interval('5m')), + 'ttl' => setv(T_DELAY, 0, 0, undef, interval('5m')), 'zone' => setv(T_FQDN, 1, 0, undef, undef), # Unused variables. 'login' => setv(T_STRING, 0, 0, 'unused', undef), @@ -5200,19 +5200,17 @@ sub nic_gandi_examples { o 'gandi' The 'gandi' protocol is used by the LiveDNS service offered by gandi.net. - Description of Gandi's LiveDNS API can be found at: https://api.gandi.net/docs/livedns/ - Available configuration variables: * password: The Gandi API key. If you don’t have one yet, you can generate your production API key from the API Key Page (in the Security section). Required. * zone: The DNS zone to be updated. Required. * ttl: The time-to-live value associated with the updated DNS record. - Optional; defaults to 3h. + Optional; uses Gandi's default (3h) if unset. Example ${program}.conf file entries: ## Single host update.