How do you solve dynamic DNS?

Have done it via bash scripts for years. Never had a problem. Since a few months i use https://github.com/qdm12/ddns-updater

used a bash script and a cron job for a long time, now the whole topic is one of the projects i regularly rewrite whenever I want to get my hands dirty with a new programming language or framework.

Cloudflare DDNS updated by ddclient on my OpnSense router. Cloudflare happens to be my current domain registrar. Honestly, my IPv4 doesn't change that often. And when I used to be on Comcast, they assigned a block of IPv6 addresses and the router dealt with that. Unfortunately, I now have Quantum Fiber who only assign a single IPv6 address, so I gave up on IPv6 for now.
- Just a practice I've had over the years with domains: separate your registrar and your DNS. If one goes down, or out of business, you can fix it if you still control the other and its accessible. If you have both of them in one place, it's really hard to get that domain transferred.

Ddclient has done the trick for me, and my registrar supports it with an API
- I set it once like 6 years ago and forgot it wasn't something pre-installed and configured until I saw your comment. I was reading through the comments looking for the "you don't need to do anything, ddclient takes care of it"

My ip updates maybe once every three months or so, but what i did was just write a script that checks the current ip and updates the domain registrar. My domain is on cloud flare, and they have an API through which I can do it. It's literally one POST request. There are solutions out there but I wanted a really simple solution I fully understand so I just did this. Script runs in cron every few hours and that's it.

Have you heard of the kuadrant project? It is for kubernetes and has a dynamic DNS element. Kuadrant.io
- Probably good, but I want to stay away from anything related to Kubernetes. My experience is that it's an overkill black hole of constant debugging. Unfortunately. Thanks though!
- Interesting, this seems to have better documentation and feedback than the external-dns operator
  
  It leans on the external-dns operator in it's DNS operator.

I would go for registering my own domain and then rent a small vps and run debian 12 server with bind9 for dns + dyndns.
If you don't want to put the whole domain on your own name servers then you can always delegate a subdomain to the debian 12 server and run your main domain on your domain registrators name servers.
edit:
https://github.com/qdm12/ddns-updater
If your registrar is supported the ddns-updater sounds a lot easier.

Desec + Nginx Proxy Manager as a reverse proxy. Solves ddns and https with a letsencrypt wildcard cert.
- Hadn't heard about deSec until now, seems to be run by some cool privacy minded folks in Germany:
  https://desec.io/

@sith
If this is useful we had a bit of a conversation about DynDns options a while back. Im currently using Hetzner with my subdomain names being dynamically updated.
lemmy.ml/post/18477306