dns: T5144: Relocate ddclient template path for consistency with config path

2023-06-04T05:34:38+00:00

dns: T5144: Restrict dualstack for dyndns2 protocol to dyn.com

2023-06-04T05:21:12+00:00

ddclient implementation of dualstack for dyndns2 protocol is targeted for dyn.com (dyndns.org) only. Dualstack won't work for other servers supporting dyndns2 protocol (for example, dyn.dns.he.net).

dns: T5144: Modernize dynamic dns operation

2023-06-04T02:54:03+00:00

Apply next round of configuration tree updates to 'service dns dynamic' with the following changes: - Migrate `service dns dynamic interface [use-web]` to `service dns dynamic address ` or `service dns dynamic address web [web-options]` This communicates the intent that dynamic dns IP address is detected in only one way - using the `` or using an external web request, not both. - When using external web request, (`service dns dynamic address web`), external url is optional (`web-options url`). Ddclient defaults are used when unspecified, - Rename all config `login` to `username` for consistency and also to align better with alternative ddclient backends in consideration. - Apply global 'ipv6-enable' to per service 'ip-version: ipv6'. Selecting usage of IPv4 or IPv6 (or both simultaneously) is now at per service (protocol) level instead of global level. This allows more control on the ability to select IPv4 in some cases and IPv6 in some other cases wherever supported by the underlying ddclient protocol. - While the IP address (and by extension, the detection mechanism) is global, the way it is applied to a particular ddclient protocol depends on whether it supports IPv4 or IPv6 or both. - Related to the above, this also prevents generating incorrect config file (`ddclient.conf`) with multiple global sections leading to an unpredictable behavior of ddclient. - Implement provider (protocol) specific custom tweaks whenever possible (e.g., `zone`, `username`, `server` are not necessary in all cases). - Move service name from a combination of 'protocol' (with protocol config autodetected) and custom (with protocol config specified) to a single 'service' key. This allows for consisent setup of multiple config for the same ddclient protocol (with different options and credentials). This also avoid ambiguity with usual networking term 'protocol' and ddclient specific term 'protocol' (and can change with a move to a different backend). - Apply upfront XML constraints and validations consistently wherever applicable. - RFC2136 specific change: Rename rfc2136 config `record` to `host-name` for consistency. - Cloudflare specific change: While ddclient still supports authenticating with email and global auth key, skipping `username` in config will indicate the intent to use API token authentication (with special 'token' literal as `username`).

T5219: ddclient: Cloudflare doesn't require login

2023-05-12T09:33:09+00:00

dns: T4353: fix Jinja2 linting errors

2022-04-16T10:13:06+00:00

ddclient: T3897: bugfix smoketest

2021-10-21T18:31:28+00:00

ddclient: T3897: Add option for IPv6 Dynamic DNS

2021-10-18T15:25:20+00:00

ddclient: T3422: Allow zone property with cloudflare protocol

2021-03-24T16:44:27+00:00

Allows Dynamic DNS services with custom names to use the zone field if the protocol is set to cloudflare (cherry picked from commit 5ab6c20f8acd4dda1870b9a71fe73129d2f78b24)

vyos.template: T2720: always enable Jinja2 trim_blocks feature

2020-11-27T14:41:17+00:00

ddclient: T2858: migrate to get_config_dict()

2020-09-13T11:17:03+00:00

vyos-1x.git/src/conf_mode/dynamic_dns.py, branch yevhen-secrets