I run ddclient on a local machine and it updates my Cloudflare DNS records if my IP changes.

OPNSense has it built in too, if you use it. So does PFSense, I think. Been a while, might be misremembering.

I use duckdns.org , but if you are trying to host a webpage I totally recommend using Cloudflare, Cloudflare tunnels and a reverse proxy like nginx.

Setting it up may be a bit tricky, but it is a gamechanger. I followed Ibracorp's guides and I had no problem.

I host my own ddns server in a debian container https://wiki.debian.org/DDNS

I've been using freedns.afraid.org for about a year now.

DNS managed by Cloudflare, and cf-ddns

I'm using DuckDNS, it has a plugin for pfSense / OpnSense.

I use a Cloudflare tunnel rather than a dynamic DNS provider. Some in the self hosting community are opposed to Cloudflare, but I appreciate the tools they provide (especially Zero Trust so I can put my self hosted apps behind Okta).

If you only need public access to things like HTTP or SSH you don’t necessarily need to run dynamic ip and just setup Cloudflare Tunnels. So far I haven’t needed to put anything public that doesn’t run on the provided tunnels.

I use DuckDNS. There's been only one outage for the ~2 years I've been using it and it's free. I also use DuckDNS to acquire the SSL certificates for the reverse proxy.

your domain provider probably has an api to update dns records i use cloudflare with their api because then i can hide my ip behind their proxy or if i don't have a public ip i can use their tunnels

Does your domain provider have a DDNS service? I buy my domains from namecheap.com and use their DDNS service for exactly what you're describing.

First step would be to ensure that you can do port forwarding.

1. Check if your IP address isn't a private one or CGNAT.
2. Now set up reverse proxy and try connecting to your service. If it connects, you are okay.
3. Now this is something i didn't know could happen but it did end up happening to me. I was happily port forwarding for a few months, until suddenly my port forwarding stopped working. Now I called my ISP, they said they did nothing(my ISP is a few guys who have no Idea about what they are doing, the other option to them is 512kbps DSL connection) at this point all my ingress ports are blocked and even outgoing ssh is blocked. Then the new month starts and everything is working again. I looked at my ISP website to get an idea of what may have caused this and the case seems to be that it was the first time I crossed 100GB in uploading. So my ISP has configured things such a way that port forwarding only works for the first 100GB of uploading.

This is why I strongly recommend cloudfare tunnel or any other similar solution.

The easiest thing to do is to use https://www.duckdns.org/ and then point your domain as a CNAME to this duckdns subdomain.

If you're using godaddy, you can use a script to do your own dynamic DNS:

https://www.instructables.com/Quick-and-Dirty-Dynamic-DNS-Using-GoDaddy/

I use this container, favonia/cloudflare-ddns, for Cloudflare and my domain.

My IP isn’t technically static but it hasn’t changed in the 3 years I’ve been with this ISP.

dedyn.io

@starkcommando When I didn't have a static IP I was using CloudFlare for this with my own domain.

I use myfritz.net for my homeserver. It is included in the routers of AVM 🐱

Afraid.org is what I've been using ever since dyndns started charging big prices for what used to be free.

DNS-O-Matic (recommended by CloudFlare, among others) combined with SWAG and Authelia will handle dynamic DNS, reverse proxying, SSL certificates, and MFA. SWAG (nginx, Let's Encrypt and Certbot) and Authelia (MFA) run nicely in a 2 container Docker stack.

Mine have been running for ~18 months on my NAS, though I have a fixed IP so no longer use a DDNS provider.

@starkcommando@lemmy.world dyndns worked fine. Duckdns is a preferred among self hosters. Also your domain name provider might also offer dynamic dns sometimes

I use cloudflare and have a dyndns client running on my synology nas

https://www.duckdns.org but to be fair I have not properly configured it in #opnsense yet!

Aside from a brief scare a couple of months ago, when the owner/operator was unreachable and the configuration interface and some automatic update paths were not working, I have been using afraid.org, and it has proven to be a stellar service, and free for basic needs.

I've been using https://dnsomatic.com/ for a long while now. It updates Cloudflare which manages my DNS. It updates DNS at other providers too which is useful.

My router is able to send DDNS updates to it.

I pay an extra £1 a month to my ISP to get a static address. Figured it's well worth having no hassle.

I just have a cron script running on a machine that does something like this every 10 seconds

C_IP=`dig +short my.domain`
IP=`curl https://api.ipify.org`
if(C_IP != IP) {
    updateRoute53(IP)
}

This is just for my main home server. Gets the job done because if it's out of date for a few seconds nothing matters.