chore(deps): update timothyjmiller/cloudflare-ddns docker tag to v2.0.2 #38
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/timothyjmiller-cloudflare-ddns-2.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
2.0.0→2.0.2Release Notes
timothymiller/cloudflare-ddns (timothyjmiller/cloudflare-ddns)
v2.0.2: — Fix Address Family Selection in Cloudflare TraceCompare Source
🐛 Bug Fix: Address Family Mismatch on Dual-Stack Hosts
On dual-stack hosts (e.g. Docker with
--net=hostand IPv6 enabled), the primary Cloudflare Trace endpoint (api.cloudflare.com) could resolve via the wrong address family — for example, connecting over IPv6 when detecting an IPv4 address. This caused the trace endpoint to return the wrong IP.What Changed
🔀 Literal IP trace URLs are now primary
Primary trace endpoints now use literal IPs per address family to guarantee correct address family selection:
https://1.0.0.1/cdn-cgi/tracehttps://[2606:4700:4700::1001]/cdn-cgi/traceThis ensures the HTTP connection is made over the correct protocol, so the detected IP always matches the intended address family.
🛡️ Hostname-based fallback for WARP/Zero Trust
The
api.cloudflare.comendpoint is retained as a fallback for environments where literal IP requests are intercepted (e.g. Cloudflare WARP or Zero Trust). Previously this was the primary endpoint.⚙️ Upgrade Notes
IP4_PROVIDERandIP6_PROVIDERenvironment variables continue to work as before.Full Changelog: https://github.com/timothymiller/cloudflare-ddns/compare/2.0.1...2.0.2
v2.0.1: — Rewritten in RustA feature-complete dynamic DNS client for Cloudflare, written in Rust.
Highlights
🐛 Bug Fix: Incorrect IP Detection via Cloudflare Trace
Users behind certain network configurations could see Cloudflare infrastructure IPs (e.g.
104.18.x.x) set as their DNS record instead of their real public IP.What Changed
🌐 Trace endpoint URL changed to
api.cloudflare.comBefore: Requests went to literal IPs
1.1.1.1and1.0.0.1, which some ISPs and network equipment intercept.After: Primary requests now go to
https://api.cloudflare.com/cdn-cgi/trace, which resolves via standard DNS and avoids interception. Literal IP fallbacks are retained for environments where DNS isunavailable.
🔀 Split dialer for address family isolation
IP detection now uses dedicated HTTP clients per address family — IPv4 detection binds to
0.0.0.0, IPv6 detection binds to::. This prevents the system from connecting via the wrong protocol (e.g. reachingCloudflare over IPv6 when detecting your IPv4 address), which could return the wrong IP.
🛡️ Global unicast validation on all detected IPs
All remote IP detection providers (Cloudflare Trace, Cloudflare DoH, ipify, custom URL) now validate that detected addresses are global unicast before accepting them. Private, loopback, link-local, multicast,
documentation, and CGNAT addresses are rejected with a warning.
☁️ Default IPv4 provider changed to
cloudflare.traceBoth IPv4 and IPv6 now default to
cloudflare.trace, keeping IP detection within the Cloudflare ecosystem. Users can still override viaIP4_PROVIDERandIP6_PROVIDER.⚙️ Upgrade Notes
ipifyas a workaround for incorrect IP detection can switch back tocloudflare.traceif desired.IP4_PROVIDERandIP6_PROVIDERenvironment variables continue to work as before.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
chore(deps): update timothyjmiller/cloudflare-ddns docker tag to v2.0.1to chore(deps): update timothyjmiller/cloudflare-ddns docker tag to v2.0.2d6580c8efdtoc6c5dfcb21View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.