Releases: kissgyorgy/cloudflare-dyndns
v5.2 - Improved API token handling
- When the API Token is invalid, the script will print a better error message.
- There is a new
--verify-token
option to check if the token is valid beforehand, which lists the zones the token have access to. - Added
--api-token-file
option: You can now read the API Token from a file.
The file should contain only the token, without any newline characters.
Thanks @jfly for this feature!
v5.1 - removed CloudFlare IP service
The Cloudflare IP tracing service (https://1.1.1.1/cdn-cgi/trace) doesn't work anymore (or at least unreliable), it's returning 403.
Changed the default IP service to https://api.ipify.org .
v5.0 - Mac OS Support
As I'm using v5.0beta5 every day for more than a year now, it was time to release the final v5.0 version π
You can install it from Docker Hub, PyPI as before, and even from Nix!
- Support for Trust stores other than Linux.
- Better IPv6 support
- Don't save cache to disk when nothing changed. See #25
- Updated dependencies
v5.0 beta5
Don't save cache to disk when nothing changed. See #25
v5.0 beta 2
- Support for Trust stores other than Linux.
- Better IPv6 support
v4.1 - Cloudflare IPv6 trace service
- Added Cloudflare IPv6 trace service
- Require all ip services to use HTTPS
- Updated Python to version 3.10 in Docker image
Thanks @lonkey for this release!
v4.0 - IPv6 support
This is the biggest update yet!
- Now you can specify
-6
command line option to update AAAA records too. - You can delete records for missing IP addresses with the
--delete-missing
option. See issue #6 for details. - There is a new
--proxied
flag for setting Cloudflare DNS services. - The script now respects
XDG_CACHE_HOME
environment variable for saving the cache.
v3.0 - API Tokens
You can only use API Tokens now, which you can create under My Profile / API Tokens
: https://dash.cloudflare.com/profile/api-tokens. The problem with the previously used API Key is that it has global access to your Cloudflare account. With the new API Tokens, you can make the script permissions as narrow as needed.
Upgrading from earlier versions and using API Tokens is highly recommended!
The --domains option
is now gone, because it made no sense (it only existed for reading from the envvar), but you can use the CLOUDFLARE_DOMAINS
envvar the same as before.
v2.1 PyPI release
Now you can install the script from PyPI simply with:
$ pip install cloudflare-dyndns
This will install a script called cloudflare-dyndns
.
Or you can still just download the binary version or Docker container and use those.
v1.1 - Cloud native
Makes it possible to set the list of domains to update from the CLOUDFLARE_DOMAINS
environment variable.
There is also a Docker image available on DockerHub in case you want to run it in a Kubernetes cluster or something π