I selfhost some tools and use duckdns for names resolution but it does not seem to be working today. My ISP updated some things on there end last night and I updated my local unbound server so I’m not sure which if either of these is also playing a role but I cant seem to access duckdns. I have tried to connect to it on my phone network outside of my isp’s control and cant which leads me to believe that duckdns is down?
I was using it as a free domain for local things. I had a local address stored in duckdns as *.example.duckdns.org -> 192.168.1.x which pointed to an nginx reverse proxy that I then used to point at different services I host locally. It worked with letsencrypt so I could use https. I bought a domain from namecheap yesterday and have since switched to using them, with the benefit of the new domain being much shorter to type lol. I’m still working on getting letsencrypt working so that I dont have to pay for an ssl, but regular http works fine since its all internal to my network.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
selfh.st Newsletter and index of selfhosted software and apps
I was using it as a free domain for local things. I had a local address stored in duckdns as *.example.duckdns.org -> 192.168.1.x which pointed to an nginx reverse proxy that I then used to point at different services I host locally. It worked with letsencrypt so I could use https. I bought a domain from namecheap yesterday and have since switched to using them, with the benefit of the new domain being much shorter to type lol. I’m still working on getting letsencrypt working so that I dont have to pay for an ssl, but regular http works fine since its all internal to my network.
Oh I completely misunderstood! I thought it was a forwarder, not dynamic DNS. My bad! Makes total sense!