Tags: Tachi107/cloudflare-ddns
Tags
### More portable 👾 and lighter 🍃 You read that right! cloudflare-ddns is now even **lighter** 🍃! This was achieved by removing the dependency on the as-big-as-awesome simdjson library - JSON is now parsed by a simple handwritten function, since cloudflare-ddns' needs for JSON parsing are really limited. By relying on one less library, the project is now more easily compiled, especially outside of Linux, hence more **portable** 👾! Apart from that, the following fixes have been made 🔧️: - cloudflare-ddns now works on **Windows 10** and older when paired with curl 7.85.0 or newer, where it previously failed due to TLS 1.3 not being supported 🪟 - Thanks to a report by @highstrike, the configuration file will now have the correct owner and **permissions** when installed via a package manager like apt 🔒 So much work for what seems like such a simple program, right? Install the last release now to benefit from all the fixes and improvements!
Release 2.0.1 Little tweaks 🔧️ After more than one year, here we are again! Not much has happened since the last release, but it shouldn't be surprising: cloudflare-ddns is fairly complete at this point. Still, I have made some tweaks, namely: - Zone ID **caching** is now fixed when using cloudflare-ddns to update multiple record names; each record's zone ID is now stored in a different file 🔧️ - The `cloudflare-ddns(1)` manual page is now written in **mdoc** instead of Ronn-markdown. This leads to easier and faster builds (`ronn-ng` is not required anymore), and a better looking man page 📝 - Small files have been relicensed from the CC0-1.0 to the **FSFAP** license, since the CC0 is considered problematic for some 📜
Release 2.0.0 Simpler 💡️ more complete 🌍️ more reliable 🪨️ Only two months passed from the last release, but we've already reached version **2.0.0** 🎉️ This release is less ground-breaking than the previous one, but a lot has improved nonetheless. Thanks to one of my last braincells I've been able to drop the need for the **Zone ID**! This means that you'll no longer have to search that string of random text in Cloudflare's web UI; it will be automatically inferred by the record name 💡️ Since release 1.0.0 someone actually started using this tool, and with new users came new issues. Thanks to @stephanlachnit's help, **IPv6** and AAAA record are now better supported. In particular, the tool will do the Right Thing when your server will have both an IPv4 and an IPv6 address, and is now also able to automatically update both A and AAAA records if they exist 🌍️ Lastly, cloudflare-ddns now **handles errors** better: it will print more meaningful error messages, fail less frequently and overall be more solid 🪨️
Add threads as a dependecy, add notice DoH logs Adding 'threads' as a dependency fix a linking error on Debian 10, and I also noticed that in that Debian release libcurl gets verbose on its own when doing DNS over HTTPS lookups because of curl/curl#3660.