I would like to host my own web server with a domain name I purchased but my public IP isn’t static.
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 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 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
I’ve been using freedns.afraid.org for about a year now.
I’ve also been on freedns.afraid.org for many years. Back when I switched from dyndns, it wasn’t possible to get Let’s Encrypt certificates on afraid.org’s domains, but that might have changed. I worked around it by taking a domain I already owned and using a CNAME to point it at my afraid.org domain.
I use Let’s Encrypt on my domains, but they’re domains that my afraid.org subdomains point to.
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).
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 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.
I also use duckdns, but in the last year it went down like twice or something. Its good but not really reliable.
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…
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.
I have NameCheap as well. I found their Windows client after I made this post. I’m still curious is there are better services out there. It seems Cloudflare may have the best tools for security for a webserver, i.e. hiding the real IP address.
I use namecheap and dd client. Happy to share my config file if you need if.
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
Cloudflare tunnels is the way to go for small self hosted content. You’re hiding behind their ddos protection and your IP / location remains hidden from end users.
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/
https://www.duckdns.org but to be fair I have not properly configured it in #opnsense yet!
@starkcommando When I didn’t have a static IP I was using CloudFlare for this with my own domain.
Afraid.org is what I’ve been using ever since dyndns started charging big prices for what used to be free.
I use this container, favonia/cloudflare-ddns, for Cloudflare and my domain.