I’m finally moving my selfhosting experiments from a VPS to a physical machine in my house but, since I don’t have a static IP address, I opted to use the dynamic dns service offered by Cloudflare.

On their official website I’ve seen suggested ddclient but I haven’t find that much information on which labels should I add to set it up. Therefore, I’ve also found this docker image that seems pretty clean and easy to set up, but the video talking about it was of 3 years ago and I’ve seen that the github repository has been archived last year…

Which option (not necessarily among the two above) do you prefer to set up your Dynamic DNS with Cloudflare? (I don’t know if this can be an important information to add or not, but the Linux server I’m using is running NixOS)

  • Arthur Besse@lemmy.mlEnglish
    94·
    11 months ago

    screenshot of Wargames computer saying "A strange game. The only winning move is not to play"

    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?

    • shaked_coffee@feddit.itOPEnglish
      2·
      11 months ago

      That’s why I didn’t want to use Cloudflare Tunnels, but just Dynamic DNS. I though that they had access to the stuff you transfer only if you use their tunneling feature and for the reasons you said is something I would prefer to avoid.

      The thing is that I bought my domain on Infomaniak and most of the self-hosting tutorials I’ve seen recommend Cloudflare. Would you suggest something different?

      • shaked_coffee@feddit.itOPEnglish
        1·
        11 months ago

        EDIT: I just realized that ddclient (that I was already considering to set up ddns with cloudflare) also supports Infomaniak directly! (I don’t know how before making this post I didn’t saw it 😅) So I’ll probably go for that way in order to cut out Cloudflare from the equation and rely on one external company less. Thank you :)

      • Arthur Besse@lemmy.mlEnglish
        7·
        11 months ago

        cloudflare’s service puts them in the middle - so, HTTPS doesn’t encrypt traffic between the browser and your server anymore, but instead between the browser and CF, and then (separately) between CF and your server. CF is an antidote to intelligence agencies’ problem of losing visibility when most of the web switched to HTTPS a decade ago.