# Flint2: Broken Cloudflare DDNS plugin **URL:** \ **Category:** Router\ **Created:** [February 27, 2024, 1:01am UTC](https://forum.gl-inet.com/t/flint2-broken-cloudflare-ddns-plugin/39096 "2024-02-27T01:01:34Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![bonez](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bonez/32/15897_2.png) [@bonez](https://forum.gl-inet.com/u/bonez)\ **Post date:** [February 27, 2024, 1:01am UTC](https://forum.gl-inet.com/t/flint2-broken-cloudflare-ddns-plugin/39096/1 "2024-02-27T01:01:34Z")
There was a thread discussing broken DDNS plugins [here](https://forum.gl-inet.com/t/flint-2-gl-mt6000-broken-ddns-plug-ins/35931/7), but it turned into an argument about GPL so it was closed with a comment from GL iNet staff that the scripts would be fixed. This still hasn’t happened. I’ve just purchased this router and need the ability to update Cloudflare using the DDNS packages, but I can’t. Does anyone have a workaround, or can staff comment on when the package will be fixed? ---
**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\ **Post date:** [February 27, 2024, 1:03am UTC](https://forum.gl-inet.com/t/flint2-broken-cloudflare-ddns-plugin/39096/2 "2024-02-27T01:03:01Z")
Cloudflare ddns? Can you give me a link of what is that? ---
**Author:** ![bonez](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bonez/32/15897_2.png) [@bonez](https://forum.gl-inet.com/u/bonez)\ **Post date:** [February 27, 2024, 1:51am UTC](https://forum.gl-inet.com/t/flint2-broken-cloudflare-ddns-plugin/39096/3 "2024-02-27T01:51:58Z")
Hi alzhao, Here is some instructions on how to configure it using OpenWRT - [link](https://alexskra.com/blog/dynamc-dnsddns-with-openwrt-and-cloudflare/) Also some basic information from [Cloudflare](https://www.cloudflare.com/en-au/learning/dns/glossary/dynamic-dns/) As per the previous discussion on these forums that I linked in the post above, it appears the `gl-sdk4-ddns` package contains outdated scripts. I managed to find a workaround, and that was to do the following: - Remove gl-sdk4-ddns - Download [https://downloads.openwrt.org/releases/23.05.2/packages/aarch64\_cortex-a53/packages/ddns-scripts\_2.8.2-42\_all.ipk](https://downloads.openwrt.org/releases/23.05.2/packages/aarch64_cortex-a53/packages/ddns-scripts_2.8.2-42_all.ipk) and install it manually - Download [https://downloads.openwrt.org/releases/23.05.2/packages/aarch64\_cortex-a53/packages/ddns-scripts-cloudflare\_2.8.2-42\_all.ipk](https://downloads.openwrt.org/releases/23.05.2/packages/aarch64_cortex-a53/packages/ddns-scripts-cloudflare_2.8.2-42_all.ipk) and install it manually It appears to be working now, but it took a bit of mucking around. It has survived a few router reboots. ---
**Author:** ![MeToo](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/m/7feea3/32.png) [@MeToo](https://forum.gl-inet.com/u/MeToo)\ **Post date:** [February 27, 2024, 6:35pm UTC](https://forum.gl-inet.com/t/flint2-broken-cloudflare-ddns-plugin/39096/4 "2024-02-27T18:35:06Z")
Thank you @bonez, I appreciate your primer on setting up DDNS. In addition to Cloudflare, it looks like it can work with a bunch of other DDNS providers. My GL.iNet device is behind a NAT modem, so the WAN interface is assigned a private IP address. How do I configure OpenWrt DDNS to report my public WAN IP? ---
**Author:** ![MeToo](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/m/7feea3/32.png) [@MeToo](https://forum.gl-inet.com/u/MeToo)\ **Post date:** [February 27, 2024, 11:26pm UTC](https://forum.gl-inet.com/t/flint2-broken-cloudflare-ddns-plugin/39096/5 "2024-02-27T23:26:09Z")
May I answer my own question? Under ‘Advanced Settings’ there is an option for the DDNS updater to use a query a URL to return the current IP address. For example [http://checkip.dyndns.com](http://checkip.dyndns.com) returns back your current public IPv4 address. Nice! ![ddnsUntitled](https://forum-static.gl-inet.com/original/2X/6/6e8f0f202242be7d9210db22827bac59ea1c24d2.png) ---
**Author:** ![blackbox](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/b/c2a13f/32.png) [@blackbox](https://forum.gl-inet.com/u/blackbox)\ **Post date:** [February 28, 2024, 4:29am UTC](https://forum.gl-inet.com/t/flint2-broken-cloudflare-ddns-plugin/39096/6 "2024-02-28T04:29:09Z")
If you self-host a website then you’ll probably want to use something like Cloudflare, since they’ll hide your IP address, optimize content delivery and provide DDoS mitigation. But if your ISP doesn’t provide static IP addresses then you’ll need to use something like the [Cloudflare DDNS package](https://openwrt.org/packages/pkgdata/ddns-scripts-cloudflare) to update your websites [DNS A record](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-a-record/) every time your IP address changes. When you forked ddns-scripts you renamed it to gl-sdk4-ddns but you didn’t change file and path names. So, gl-sdk4-ddns ends up conflicting with ddns-scripts and all of its optional add-on packages (e.g. ddns-scripts-cloudflare, ddns-scripts-cnkuai, ddns-scripts-gandi, ddns-scripts-noip) and the only solution is to uninstall gl-sdk4-ddns. If you were to rename all of the files and the paths within them then people wouldn’t need to uninstall gl-sdk4-ddns. > ddns → glddns > 95-ddns → 95-glddns > dynamic\_dns\_functions.sh → dynamic\_gldns\_functions.sh > dynamic\_dns\_updater.sh → dynamic\_gldns\_updater.sh But as I mentioned to you privately before now, it seems like gl-sdk4-ddns could have most of the ddns-scripts files removed from it now anyway, since it uses it’s own library to provide DDNS services for `glddns.com`. ---
**Author:** ![LioMajor](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/l/96bed5/32.png) [@LioMajor](https://forum.gl-inet.com/u/LioMajor)\ **Post date:** [March 17, 2025, 4:03pm UTC](https://forum.gl-inet.com/t/flint2-broken-cloudflare-ddns-plugin/39096/7 "2025-03-17T16:03:19Z")
looks like the script might not be handling authentication properly. have you tried using the api token instead of the global key? that worked for me when i had the similar issue ---
**Author:** ![LioMajor](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/l/96bed5/32.png) [@LioMajor](https://forum.gl-inet.com/u/LioMajor)\ **Post date:** [March 20, 2025, 11:49am UTC](https://forum.gl-inet.com/t/flint2-broken-cloudflare-ddns-plugin/39096/8 "2025-03-20T11:49:19Z")
Sounds like the Cloudflare DDNS plugin is having some trouble on Flint2. I’ve seen similar issues before, and sometimes switching to a different DNS resolver helps, even if it's just temporary. If you’re testing connections, make sure your ISP isn’t interfering, since some block dynamic DNS updates. Also, check if any firewall rules might be in the way—especially if you've been running any stress tests with [ipstresser](https://darkvr.su/) or similar tools. ---
**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\ **Post date:** [October 30, 2025, 3:22am UTC](https://forum.gl-inet.com/t/flint2-broken-cloudflare-ddns-plugin/39096/9 "2025-10-30T03:22:00Z")