buy a cheap domain and use afraid services, https://freedns.afraid.org/, or ydns, https://ydns.io/, with free license is a good and cheap solution.
this post was submitted on 02 Sep 2024
23 points (92.6% liked)
Selfhosted
39964 readers
379 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:
-
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!
founded 1 year ago
MODERATORS
Question - if your domain registrar has an API to update your A/AAAA records, and your router (or other home server) lets you easily update those records via the API when your public IP changes, is there a benefit to using freedns or any other DDNS service? It seems like you don't really need them if you own a domain.
I switched to cloud flare because of the downtime duckdns has. Sometimes it can get really bad.
Same. Been rock solid.
Same here. I love DuckDNS but after the third DNS outage taking down all my services I migrated to Cloudflare and haven't had a single problem since.
Yes, it's why I stopped using DuckDNS and decided to buy my own domain. I used Porkbun and got a cheap one (~$15/year?). It was super easy, and DNS results are lightning fast now; no timeouts/errors/etc. like when I was using DuckDNS.
My router supports Porkbun for DDNS; it handles updating the A/AAAA records for my domain when my IP changes, but if your router doesn't have that option, I'm sure there's a script you could run on a PC or Raspberry Pi, etc. to handle that for you.
I honestly don't know why I didn't do this sooner! I've changed DDNS providers a few times over the years and it's always a pain to update everything that references the old names. It's great having peace of mind knowing that I own the domain now and won't have to change again (even if I wanted to leave Porkbun, I could just transfer the domain registration to any number of good alternatives and not have to change my domain name).
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| DNS | Domain Name Service/System |
| IP | Internet Protocol |
| VPS | Virtual Private Server (opposed to shared hosting) |
3 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.
[Thread #947 for this sub, first seen 2nd Sep 2024, 12:55] [FAQ] [Full list] [Contact] [Source code]
DuckDNS pretty often has problems and fails to propagate properly. It's not very good, especially with frequent IP changes.
What's a better option these days? I'd be interested in trying to get rid of duckdns
Buying a domain. There might be some free services that, similar to DuckDNS in the beginning, work reliably for now. But IMHO they are not worth the potential headaches.
I have a domain... but I think DynDNS is not always available for every domain or by every domain seller?
Registrars (or DNS providers if you don't use the one that comes with your registrar) worth using have an API to manage DNS entries. That's basically all there is to DynDNS.
Thats how I've done mine.
pfSense has an updater built in so that's handled my home.mydomain.com entry for me for a long time and has handled updating duckdns too, even though it's basically only a backup at this point.
If you've got a domain, no real reason to not just handle it yourself and avoid the headaches.
In my case, there is no IP change. However, the TTL of entries seems to be 60 seconds and when Cloudfare/Google asks for the new A record, it sometimes fails. I am getting this error message from Cloudfare when I try to solve host.sub-domain.duckdns.org
EDE: 22 (No Reachable Authority): (time limit exceeded)
I used to rely heavily on duckdns and it was great for a time, but moved off them a couple of years ago because resolution became inconsistent. I've since rolled my own ddns using a script that utilizes Porkbun.com's DNS record API.
I've heard many people complain about DuckDNS. Personally use desec.io for DDNS and it's been solid.
Thanks for all your answers! I will check some of the alternatives to duckdns.