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 do this too. I proxy my DNS which means my home IP isn't exposed
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
Here we go down another rabbit hole... 😆
Right!!!! Lmao 😂 same boat as ya lol
DNS managed by Cloudflare, and cf-ddns
2nd, but with just a bash script. Also, I'm forwarding http & https to different IPs and the best thing about cloudflare is that you can restrict those ports to only be open when coming from cloudflare's proxy. I like the extra layer of security, and dislike that they can see all traffic..
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).
+1 for tunnels, easy to use and no port forwarding required
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
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.
Where are the settings for these tunnels located in Cloudflare? I was looking around the website last night but didn't have any luck.
It's confusing. I think they are under zero trust now
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.
How gave you set it up out of curiosity?
If you mean automatically update IP part, duckdns website has a very comprehensive guide.
If you mean getting a free SSL certificate, you can use acme.sh (this is what I used) which has integrated support for duckddns (To use let's encrypt you need to use --server letsencrypt in your command)
I also use duckdns, but in the last year it went down like twice or something. Its good but not really reliable.
I used duckdns for my jellyfin server, but after a week or so I started getting malicious site warnings from Firefox, and had to ‘accept the risk and continue’ every time. Ended up going back to noip. It’s a pain to renew every month, but I haven’t had any other problems with it.
I use noip as well, but because I only have an IP camera on that network, and the camera has built-in DDNS support for noip. But I hate it having to renew monthly.
What do you mean renew every month?
You need to confirm each month that you’re still using that url if you’re in free tier. Otherwise it won’t be registered to you
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 also use this.
Have had to update it in tiny ways in the last ~ 7 years?
dedyn.io
My IP isn’t technically static but it hasn’t changed in the 3 years I’ve been with this ISP.
This. But I use namecheap and the built in tool on pfsense to keep an A record up to date if it ever changed.
I have NameCheap as well. I was trying to set this up with the ddclient on OPNSense but the logs suggested it couldn't connect to NameCheap. What do you need to authenticate other than the DDNS passcode supplied by NameCheap?
Oof. Set this up years ago now..
Add the hostname IE public Add the domain name IE starkcommando.com
This will be public.starkcommando.com
Leave username blank (this was a gotchya for me, if I recall correctly)
Then put the generated namecheap ddns password (not your account password) that matches the record in.
All set.
I use this container, favonia/cloudflare-ddns, for Cloudflare and my domain.
First step would be to ensure that you can do port forwarding.
This is why I strongly recommend cloudfare tunnel or any other similar solution.
I use cloudflare and have a dyndns client running on my synology nas
I use myfritz.net for my homeserver. It is included in the routers of AVM 🐱
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
Afraid.org is what I've been using ever since dyndns started charging big prices for what used to be free.
Before, I used to use duckdns. Completely free and super simple
Nowadays I just have a docker container that updates my A records on my domain directly through namesilo's API. Took like 5 mins to set up the config
I'm still using noip.com. There may be better/cheaper options these days, but this has worked well for me for years, and I don't see the need to change.
I pay an extra £1 a month to my ISP to get a static address. Figured it's well worth having no hassle.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!