I've been using this image with different providers for years. I would highly recommend it.

https://hub.docker.com/r/qmcgaw/ddns-updater

I wrote a bash script this that updates cloudflare using their API if the public has changed, and just have it running with crontab.

It's been running for 6 years now without issue so I recommend this

I was using that same docker image for a while but somewhat recently migrated to this: https://github.com/favonia/cloudflare-ddns

It handles 5 of my domains all from the single container. Highly recommend it!

You might want to check out their Tunnels product. It might do what you want and is easy.

cloudflare is an intelligence company who's flagship product involves them mitming your TLS.

why bother self-hosting, if you do it from behind cloudflare?

Here is what I used before I switched to desec.io: https://gist.github.com/haansn08/50565768c66c5fbf382b2bc2484e8a41

I use this: https://github.com/NChaves/Cloudflare_DNS_API_bash

All those do is essentially call the Cloudflare API. They'll all work reasonably well. The linked Docker image for example is essentially doing the bulk of it in this bash script which they call from a cron and some other container init logic which I imagine is to do the initial update when the container starts.

Pick whatever is easiest and makes most sense for you. Even the archived Docker thing is so simple, I wouldn't worry about it being unmaintained because it can reasonably be called a finished product. It'll work until Cloudflare upgrades their API and shuts down the old one, which you'd get months to years of warning because of enterprise customers.

Personally, that's a trivial enough task I'd probably just custom-write a Python script to call their API. They even have a python library for their API. Probably like 50-100 lines long tops. I have my own DNS server and my DDNS "server" is a 25 lines PHP script, and the client is a curl command in a cronjob.

DDNS is a long solved and done problem. All the development is essentially just adding new providers.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

5 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.

[Thread #373 for this sub, first seen 25th Dec 2023, 05:15] [FAQ] [Full list] [Contact] [Source code]

but I haven’t find that much information on which labels should I add to set it up.

I’ve not automated creation of records for new services, but I’ve made it easier for myself by making hostname.domain.ext the dynamic DNS (managed by a simple cron job with curl commands interacting with the API), and all service.domain.ext just CNAME to the main record.

I don’t think I’ll be automating the creation of the CNAME records because something tells me I’d end up leaving a bunch of dead service DNS records behind.

Been using this slick tool for a while now.

https://github.com/troglobit/inadyn

Easier to configure and better error codes than ddclient in my opinion.