Selfhosted @lemmy.world zako @lemmy.world 2 mo. ago

Anyone with problems with duckdns DynDNS?

I feel that sometimes resolution of sub-domain.duckdns.org and host.sub-domain.duckdns.org fails with empty result or even timeout result. Tested resolution against Google and Cloudfare DNS servers.

Do you have a similar behaviour?

17 comments

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.
- 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 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.
- Same. Been rock solid.
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).
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.
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]
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.
No-ip.

I've been using them for about 15 years now. Started when I self hosted at home with the free service and even though I moved to a VPS I still use them ($32 USD / year, dedicated TLD, dedicated IP). I can add redirects, temp static landing page, etc etc.

I've had a SINGLE outage of their service in that time.

They also have free services as well, dynIP clients for Win & Lin, and their shit works. Most DD-WRT / OpenWRT images also support it.