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?

  • Emotet@slrpnk.netEnglish
    3·
    2 个月前

    DuckDNS pretty often has problems and fails to propagate properly. It’s not very good, especially with frequent IP changes.

    • zako@lemmy.worldOPEnglish
      1·
      2 个月前

      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)

      • Emotet@slrpnk.netEnglish
        4·
        2 个月前

        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.

        • zako@lemmy.worldOPEnglish
          2·
          2 个月前

          I have a domain… but I think DynDNS is not always available for every domain or by every domain seller?

          • 2xsaiko@discuss.tchncs.deEnglish
            5·
            2 个月前

            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.

            • TVA@thebrainbin.org
              2·
              2 个月前

              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.