Good FOSS software and reliable service providers? Etc.
Afraid has a curl update. Cron job. It’s that simple.
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”
Good FOSS software and reliable service providers? Etc.
Wow much detail. You’re gonna get so much help.
Actually I did. Not thanks to you though.
Ddns-updater and porkbun.
Have done it via bash scripts for years. Never had a problem. Since a few months i use https://github.com/qdm12/ddns-updater
Any registrar worth using has an API for updating DNS entries.
I just found this with a quick search: https://github.com/qdm12/ddns-updater
I would recommend OVH for DNS, they have an API and are on the list for that tool. Also you can use the API to get lets encrypt certificates
exactly. I literally have a bash script that calls the API triggered by cron every 30 minutes. That’s it. Are people seriously using a freaking docker container for this?
It’s easy to set up and also keeps a history
I just dump the changes with timestamps to a text file. Notifications for IP changes get sent to matrix after the DNS record is updated.
Ah, a history would be nice. I’ve been thinking of keeping some stats to monitor when the connection goes down, and how often my IP changes.
Fortunately I’ve kept the same IP since i changed ISPs a few months ago.
Personally I still think docker is overkill for something that can be done with a bash script. But I also use a Pi 4 as my home server, so I need to be a little more scrupulous of CPU and RAM and storage than most :-)
Even if it is docker it’s still a bash script or something in the container right? Or are people referring to the docker CLI directly changing DNS records somehow?
My best guess is the reason to involve docker would be if you already have a cluster of containers as part of the project. Then you can have a container that does nothing but manage the DNS.
Looks good. Thanks!
my router uses openwrt which supports dynamic DNS updating on its own for multiple providers, I currently am through namecheap on it.
Have you heard of the kuadrant project? It is for kubernetes and has a dynamic DNS element. Kuadrant.io
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.
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!
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:
If your registrar is supported the ddns-updater sounds a lot easier.
https://www.cloudns.net/ Makes dynamic DNS very easy.
I use http://www.duckdns.org/
Me too. I use uptime kuma to send the api request. then I also get uptime status 🙂
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.
If you don’t need actually public DNS, something like Tailscale might be an option.
Cloudflare-ddns in docker
afraid still works like a charm. cloudflare is ok. duckdns is cool.
