Best way to set up cloudflare dynamic DNS in late 2023?

Comments

• FlexibleToast@lemmy.world ⁨10⁩ ⁨months⁩ ago

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

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

  source
• bash@sh.itjust.works ⁨10⁩ ⁨months⁩ ago

  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

  source

  • bless@lemmy.world ⁨10⁩ ⁨months⁩ ago

    Same but powershell. Works like a charm runs every 5 minutes

    source
• notannpc@lemmy.world ⁨10⁩ ⁨months⁩ ago

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

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

  source
• Max_P@lemmy.max-p.me ⁨10⁩ ⁨months⁩ ago

  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.

  source
• kpw@kbin.social ⁨10⁩ ⁨months⁩ ago

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

  source
• grimer@lemmy.world ⁨10⁩ ⁨months⁩ ago

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

  source

  • shaked_coffee@feddit.it ⁨10⁩ ⁨months⁩ ago

    I’ve seen it mentioned in a bunch of videos and articles, but I didn’t like the idea of Cloudflare scanning all the stuff that is transferred from and to my server. If I opt just for their DNS service and update it through the API they can’t do that, right?

    source

    • Nyfure@kbin.social ⁨10⁩ ⁨months⁩ ago

      No, then they only handle your DNS setup, which is still okay in my eyes.
      Its certainly far away from scanning all HTTP traffic. Not to forget the juicy metadata they get about the users across a big chunk of the internet, perfect tracking machine in a neat package with easy access by the government.

      source
• Static_Rocket@lemmy.world ⁨10⁩ ⁨months⁩ ago

  Been using this slick tool for a while now.

  github.com/troglobit/inadyn

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

  source
• rammjet@lemmy.world ⁨10⁩ ⁨months⁩ ago

  I use this: github.com/NChaves/Cloudflare_DNS_API_bash

  source
• chiisana@lemmy.chiisana.net ⁨10⁩ ⁨months⁩ ago

  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.

  source

  • shaked_coffee@feddit.it ⁨10⁩ ⁨months⁩ ago

    I think that this could be the cleanest solution, could you share the curl command you used to interact with the API? (Of course replacing your actual access token with ** etc.)

    source
• Decronym@lemmy.decronym.xyz ⁨10⁩ ⁨months⁩ ago

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

  Fewer Letters	More Letters
  DNS	Domain Name Service/System
  SSL	Secure Sockets Layer, for transparent encryption
  TLS	Transport Layer Security, supersedes SSL

  ---

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

  source