I would like to host my own web server with a domain name I purchased but my public IP isn’t static.
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
Jup, I use my pfSense as DDNS client with Cloudflare
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
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.
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 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
I’m using DuckDNS, it has a plugin for pfSense / OpnSense.
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.
Look under the Zero Trust category and then once there you’ll see another menu item called Access. There you’ll find Tunnels, in addition to Tunnels you can add an Application in the same Access menu to create policies that only allow certain clients to connect.
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.
Does it work for RDP?
Sort of? https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/use-cases/rdp/ - I have no idea how to do it though.
I’ve had SSH and VNC sessions rendered in web pages with tunnels, but never RDP.
I would prefer to use TailScale (www.tailscale.com) for something like RDP though, much easier to configure / set up and again you’re hiding behind their infrastructure.
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
Tunneling is one of the better options out there tbh.
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.
I also use duckdns, but in the last year it went down like twice or something. Its good but not really reliable.
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.
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
deleted by creator
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.
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.
Cloudflare has a lot of great tools and provides service to most of the internet. Some folks don’t like how much of internet traffic is routed though Cloudflare… sort of like Google and if that’s not a bother then it may be a good choice.
I use namecheap and dd client. Happy to share my config file if you need if.
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?
First step would be to ensure that you can do port forwarding.
- Check if your IP address isn’t a private one or CGNAT.
- Now set up reverse proxy and try connecting to your service. If it connects, you are okay.
- 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.