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?
You must log in or register to comment.
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.
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.
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.
