Selfhosted
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
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Let's back up some - a free dynDNS provider would not cause connection issues, unless DNS resolution itself stopped working - which is unlikely. It sounds more like the Internet you're running off of itself has issues. What in particular is making you blame the dynDNS? Who is it?
... Check duckdns constant resolution issues. There's lots of threads about their inconsistency and unreliability. Can't really complain, because it's truly free, but there's no full week that goes without issue.
Ha, if he said duckDNS I was going to recommend something more reliable like freedns.afraid.org.
That being said, the description in his post doesn't make it seem that way.
For me it seems like a very similar issue with these inconsistencies. Why would your think it does not really match? Especially given that the network connection of our server location is always fine during these down times?
Your connection being fine during downtime is a new detail not in your original post that changes the dynamics. That being said I believe my other response should be helpful.
For me it seems like to be a similar issue with the duckdns inconsistencies.
I am using dynv6.com. The reason I blame the DNS resolution is because when I have issues connecting (as if the domain is not available), it does not mean that my friends cannot connect either. The server is at a friends house who has a fiber connection and who has no issues when we habe trouble connecting again. I could be totally wrong, but to me it sounds like dynv6 has some troubles.
I also have a script running, which constantly updates dynv6 with our current IP address.
Well, it can't hurt to cross it off. You don't need to get a domain from a registrar that offers dynamic DNS, you just need to register a domain (or try another dynamic DNS like the other user suggested) and use a DNS provider that is free and offers an API. I personally use Cloudflare, there are plenty of guides for setting up a dynamic record on CF.
For registering a domain you can use an affordable registrar, I'm a Porkbun customer - for a
.comdomain it's like $11 for a year. No need to spend monthly.I looked into porkbun and it seems that they already offer a Cloudflare API for dynamic DNS. Why did you choose to separately use Cloudflare? Bit otherwise it looks promising to give it a try.
I used to use dynv6, but I started having issues about 2 years ago. DNS records would just stop resolving until I deleted and recreated them. Their forum has been broken for years, so there's no way to get support.
If you only need 5 records or less, give FreeDNS a try.