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.net
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      3 months ago

      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.worldOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 months ago

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

        • 2xsaiko@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          5
          ·
          3 months ago

          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
            link
            fedilink
            arrow-up
            2
            ·
            3 months ago

            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.