I’m new to self-hosting. All I did so far was install Ubuntu Server, enable SSH and tried setting up DuckDNS, which I could not set up automatic update of my IP following the documentation, neither updating manually through the website, which even though seems to be changed, when I ssh the domain, I get the initial IP

Anyone using DuckDNS? Is it working properly for you guys? Did I just mess something up?

What other DDNS providers would you recommend me?

  • ozymandias117@lemmy.worldEnglish
    29·
    5 months ago

    I put the curl command to update my duckdns IP in cron about 13 years ago, and have never needed to touch it once.

    It’s just worked for me

  • undefined@lemmy.hogru.chEnglish
    11·
    5 months ago

    I used to just use a script with cron to update Cloudflare DNS records but these days I don’t screw around with exposing anything to the public internet directly, I just use Tailscale.

    • HotDog7@feddit.onlineEnglish
      4·
      5 months ago

      Is there a difference between using Tailscale and Wireguard? I already have a Wireguard setup and want to know what benefits it has over Wireguard.

      • undefined@lemmy.hogru.chEnglish
        4·
        5 months ago

        They’re similar but mainly Tailscale arranges WireGuard tunnels between peers. There are tons of useful features around that functionality like being able to route specific traffic through specific hosts (“nodes” using “app connectors”); it’s even better at finding a way out of hostile networks using relays.

        Just as an example I typically use my VPS as an “exit node” so that all my traffic routes through it (which does a ton of tunnel hopping through commercial VPNs) while my wife isn’t into that at all, but both of us have Tailscale on our devices so when either of us accessing Home Assistant it’s routed directly to the host hosting it.

  • somenonewho@feddit.orgEnglish
    8·
    5 months ago

    I had used duckdns for a while back in the day. Always worked great.

    These days I have a domain at namecheap which provides a DynDNS feature as well so I’m using that.

  • yaroto98@lemmy.worldEnglish
    7·
    5 months ago

    I got my domain through namecheap. So, I just use them, they have a dynamicdns implementation. I setup a namecheapddns docker container that auto updates mine.

    • epyon22@sh.itjust.worksEnglish
      3·
      5 months ago

      Yep same DDClient is super simple to setup with name cheap. Followed ip address changes with very little if any down time. I’ve never noticed between ip changes.

  • roofuskit@lemmy.worldEnglish
    6·
    5 months ago

    Duck DNS works great… Most of the time. If you cannot accept downtime multiple times a year, get yourself a domain and a service like cloud flare instead. DuckDNS is free and you get more than you pay for, but the bar is low when the cost is zero.

    • potustheplant@feddit.nlEnglish
      4·
      5 months ago

      Or just use two dns providers. I have duckdns and desec. That latter seems to be a bit faster and has’t had any downtime for me so far.

  • plateee@piefed.socialEnglish
    6·
    5 months ago

    I have dyndns. I don’t recommend them, unless a coworker just gave you their lifetime pro account for free.

    Thanks Roody, wherever you are!

  • Brkdncr@lemmy.worldEnglish
    4·
    5 months ago

    I’ve used no-ip.com for years without issue.

    My NAS supports a few services out of the box. If you have anything like that, see what they support natively first.

  • brewery@feddit.ukEnglish
    4·
    5 months ago

    You could be behind CGNAT - I’m not sure the best way to tell but it could be the reason.

    I would also highly recommend buying a cheap domain to use - it would be the price of a coffee per year but makes life so much easier and you don’t have to depend on duckdns. You can buy through cloudflare, porkbun or many other options which you can search for a good DDNS service to update them.

    • Dran@lemmy.worldEnglish
      2·
      5 months ago

      CGNAT does have a designated range by spec. 100.64.0.0/10, which covers addresses from 100.64.0.0 to 100.127.255.255. Technically they could be using any other private address space but it would be very uncommon in a modern ISP.

  • cow@lemmy.worldEnglish
    3·
    5 months ago

    I already used desec.io for my domains back when I had static IP blocks at home so I just used the dyndns api with ddclient to update them automatically for my dynamic IP.

  • IanTwenty@piefed.socialEnglish
    2·
    5 months ago

    This might be obvious but it could be caching? Use a tool like dig to check if it’s really updated. Not had a problem with duckdns, works good.

  • harsh3466@lemmy.mlEnglish
    2·
    5 months ago

    I used duckdns for years without any issues at all. Only reason I switched is because I’m using Pangolin and tunneling instead of exposing my IP directly.