Cloudflare inadyn stopped working

[XIII]

your call, obviously.

Still it’s good to know I have this “fallback” if I fail to achieve my goal using just In-a-dyn.

So thank you for your suggestion!

 

[Vorwrath]

Had to troubleshoot a similar problem where inadyn with Cloudflare was previous working for me and broke with a router firmware update. In my case the main cause was the newer inadyn version changing the function of the "username" field to actually want the domain name (previously it was the email address of the Cloudflare account).

The minimal config that works for me is in /jffs/inadyn.conf: -

provider [email protected] {
        username = mydomain.com
        password = CLOUDFLARE_API_TOKEN
        hostname = myhost.mydomain.com
}

CLOUDFLARE_API_TOKEN is a custom API token that you create for the zone from Cloudflare's control panel, which must have the permissions Zone.Zone -> Read, Zone.DNS -> Edit

In /jffs/scripts/ddns-start (must have execute permission): -

#!/bin/sh
inadyn --once -f "/jffs/inadyn.conf" -e "/sbin/ddns_custom_updated 1" --continue-on-error "/sbin/ddns_custom_updated 1"

 

[abracadabra11]

I use the router's inadyn to dnsomatic (in the WebUI) and then dnsomatic pushes to cloudflare. No fiddling required

Can you provide an example of your setup in router settings, dnsomatic, and cloudflare?

I'm having issues getting mine setup properly.

PM if you prefer.