this post was submitted on 17 Nov 2025
50 points (96.3% liked)

Selfhosted

61451 readers
430 users here now

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Hi everyone,

Edit2: I bought a domain (1,50€ p.m.) from a European service which also offers dynDNS functionality. Just needed to adjust my NGINX config and generated new SSL-certificates via Certbot. I also built a script that only issues the update URL if the actually IP has changed. The system has been running flawlessy now for a couple of days already. No outages or any other connection issues. Learning: even though the dynDNS functionality should work stable in theory (since there is not much going on), the dynDNS service provider actually plays a big role in terms of reliability.

a couple of friends and I have a Jellyfin server running which is exposed to the internet via a reverse-proxy and https by using a free dynDNS provider.

The setup is working fine besides the dynDNS provider. We constantly face connection issues, making the dynamic DNS functionality very unreliable.

So I started looking into possible solutions and one particular would be to buy an own domain which would only cost a few bucks each month. With this I could keep the current setup and would just need to change the domain (and possibly the SSL certificate). I found a provider over which I could buy (rent?) a domain and which also provides dynDNS functionality. But I am not too sure if I understood this correctly:

  • if I have an own domain, why would I need the additional dynDNS functionality? I would guess that I would just continue updating your server's IP address to the domain name like we are doing now
  • can the provider over which I rent the domain with servers in my country actually see what our traffic is? Especially since we are streaming our movies etc.
  • is there a better way of obtaining and setting up your own domain also in terms of privacy and reliability than with a bigger company offering such services?

Thanks a lot for your feedback!

Edit: An important fact I forgot to add in my main post is that during these issues, the general server connection should be fine since it is located at a friends house and his internet connection is unaffected (e.g. we could still talk in Discord normally and he had no internet issues whatsoever)

you are viewing a single comment's thread
view the rest of the comments
[–] Coleslaw4145@lemmy.world 4 points 9 months ago

It's possible that, when the ISP revokes the public address and assigns a new one, the DNS record isn't updated immediately and still points to the old address. Then every new request would be sent to the old, invalid address.

I've got it set up on my OPNSense firewall

OPNsense has ddclient built in which solves this problem as well.