gdnsd
[rss] RSS Feed Version 3.8.3 Released 2024-09-19 Version 3.8.2 Released 2024-01-04 Version 3.8.1 Released 2023-02-22 Version 3.8.0 Released 2021-08-13 Version 3.7.0 Released 2021-06-08 Version 3.6.0 Released 2021-02-24 Version 3.5.2 Released 2021-02-23 Version 3.5.1 Released 2021-02-10 Version 3.5.0 Released 2021-01-11 Version 3.4.2 Released 2021-01-11 Version 3.4.1 Released 2020-11-20 Version 3.4.0 Released 2020-11-19 Version 3.3.0 Released 2020-09-09 Version 3.2.2 Released 2020-02-19 Version 3.2.1 Released 2019-07-19 Version 2.4.3 Released 2019-07-19 Version 3.2.0 Released 2019-05-05 Version 3.1.0 Released 2019-03-30 Version 3.0.1 Released 2019-03-04 Version 3.0.0 Released 2019-02-15 Version 2.4.2 Released 2019-02-11 Version 2.4.1 Released 2019-01-10 Version 2.4.0 Released 2018-02-15 Version 2.3.1 Released 2018-02-15 Version 2.2.5 Released 2018-02-15 Version 2.3.0 Released 2017-11-20 Version 2.2.4 Released 2016-04-14 Version 2.2.3 Released 2016-03-23 Version 2.2.2 Released 2016-01-06 Version 2.2.1 Released 2015-08-05 Version 2.1.3 Released 2015-08-05 Version 2.1.2 Released 2015-05-06 Version 2.2.0 Released 2014-12-30 Version 2.1.1 Released 2014-12-30 Version 2.1.0 Released 2014-10-14 New Repo Url 2014-10-09 Version 2.0.0 Released 2014-10-02 Version 1.11.5 Released 2014-09-10 Version 1.11.4 Released 2014-07-18 Version 1.11.3 Released 2014-05-14 Version 1.11.2 Released 2014-02-27 Version 1.11.1 Released 2014-01-11 Version 1.11.0 Released 2013-12-06 Version 1.10.1 Released 2013-10-04 Version 1.10.0 Released 2013-09-04

Version 3.2.2 Released2020-02-19

Source tarball and GPG signature available at: https://github.com/gdnsd/gdnsd/releases/

3.2.2 - 2020-02-19
    * Bugfix: In the case that a "replace" daemon takeover happened while
      unexpired ephemeral ACME challenge data was present (which is handed
      off to the new replacement daemon), the new daemon could pause for the
      entire value of "acme_challenge_ttl" (default: 10 minutes) during its
      startup sequence.  The takeover/replace process would eventually succeed
      between the two daemons, but the long wait would cause various timeouts
      for control/notification by default (e.g. gdnsdctl won't wait that long
      to report the success).