I would like to host my own web server with a domain name I purchased but my public IP isn’t static.

@vynlwombat@lemmy.world
link
fedilink
English
11Y

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

@starkcommando@lemmy.world
creator
link
fedilink
English
4
edit-2
1Y

Here we go down another rabbit hole… 😆

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.

ComMcNeil
link
fedilink
21Y

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

Bristlerock
link
fedilink
1
edit-2
1Y

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.

IcerOut
link
fedilink
11Y

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

BetterNotBigger
link
fedilink
English
21Y

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.

@starkcommando@lemmy.world
creator
link
fedilink
English
21Y

Where are the settings for these tunnels located in Cloudflare? I was looking around the website last night but didn’t have any luck.

BetterNotBigger
link
fedilink
English
11Y

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.

elscallr
link
fedilink
1
edit-2
1Y

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.

667
link
fedilink
0
edit-2
1Y

AdGuard! They even have installable profiles for Apple devices, so I get ad blocking even on mobile!

mb, DDNS. nvm

Virkkunen
link
fedilink
11Y

OP is asking about DDNS instead of DNS. They want a fixed address to their ever changing IP address.

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 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.

@Bork@lemmy.world
link
fedilink
English
21Y

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

@hagerman@lemmy.world
link
fedilink
English
71Y

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).

Entropy
link
fedilink
English
11Y

+1 for tunnels, easy to use and no port forwarding required

RedditExodus
link
fedilink
21Y

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

DunkinCoder
link
fedilink
English
11Y

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

Create a post

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:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

  • 1 user online
  • 31 users / day
  • 80 users / week
  • 216 users / month
  • 845 users / 6 months
  • 1 subscriber
  • 1.42K Posts
  • 8.13K Comments
  • Modlog