| Age | Commit message (Collapse) | Author |
|---|
|
If there is no zone option given it will be "guessed" as in the past.
This means (hostname -> resulting zone entry)
domain.com -> com
foo.domain.com -> domain.com
bar.foo.domain.com -> foo.domain.com
I have zero experience in the CloudFlare zone option what it is and what
it does. SO maybe we still have a chance to auto render this setting.
|
|
When service was deleted we tried accessing a key in the dictionary. But there
was no dictionary at all as get_config() returned 'None' instead of 'dyndns'.
|
|
Commit 967067970494c1800f ("ddclient: T1030: adjust to latest syntax")
was under the impression that ddclient 3.9.0 now handles every config
item with a comma in the end. This is unfortunately not true on RFC2136
dynamic DNS entries.
Remove commas on config template.
|
|
|
|
|
|
|
|
|
|
|
|
When deleting or changing "service dns dynamic" the cache file of ddclient
is not removed, leading to abandoned host names which might be already gone.
|
|
|
|
This bug was present since the old Vyatta days as the use-web statement
was only put into action when also "use-web skip" was defined.
The service https://ipinfo.io/ip does not place any crap in front of the
IP address so the skip statement was not used and made no sense.
|
|
JINJA2 templated missed the 'server=' statement when generating custom dynamic
DNS entries in the resulting ddclient.conf.
|
|
Since version 3.8.0 ddclient support the update of multiple ip's. The
need for running multiple ddclient instances with different
configuration files is thus no longer necessary.
More information can be found on the ddclient forum:
https://sourceforge.net/p/ddclient/mailman/message/20383414/
|
|
|
|
|
