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?
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.
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.
DuckDNS pretty often has problems and fails to propagate properly. It’s not very good, especially with frequent IP changes.
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)
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.
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)
[Thread #947 for this sub, first seen 2nd Sep 2024, 12:55] [FAQ] [Full list] [Contact] [Source code]