For dynamic updating of dns, don’t use ddclient or cron scripts on the server. Instead use inadyn.

Ddclient is more or less just dead/maintenance mode.

also using cron scripts kinda sucks and is ugly.

just use inadyn and spare yourself headache.

You’d basically just add something like this to the inadyn.conf file

provider duckdns.org {
    username         = YOUR_TOKEN
    password         = noPasswordForDuckdns
    hostname         = YOUR_DOMAIN.duckdns.org
}

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

Anything that supports bind’s built-in nsupdate.

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.

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!

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.

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.

Another free option I like is dynu.com

They have an example ddclient config in their FAQ: www.dynu.com/FAQ/Dynamic-DNS-Service#IPUpdate

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.

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.

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.

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.

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.

NoIP works great for me so far!

I’ve used duckDNS for years. A couple of years ago it started flaking out every couple of months so I migrated off it.

Another one I have seen recommended in here is afraid.org, adding it as haven’t seen it mentioned yet.

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.

I use ddclient on my vps

cloudns.net

On the off chance you’re facing issues due to CGNAT, you’d likely need to work around it with something like a cloudflare tunnel, or purchasing a cheap VPS and porting all traffic through WireGuard or similar.

I have been using duckdns for a few years without issues. It should be simple enough , just set up a cron job with your details as listed on their site where you configure it. This keeps your dns entry up to date.

I am using Dynu. It works fine and it’s free, no complaints. Their app for Linux to update periodically didn’t seem to work well from my experience, I just set up a cron job to do it instead.

DuckDNS had been unreliable when I used it, but it’s been a while. I swapped over to desec.io but their signups aren’t always open. Can highly recommend them though, and they offer many paths to update the IP, including DynDNS(2) protocol or just ddclient.

Also works with certbot for Let’s encrypt certificates using dns challenge.

I ended up using Dynv6, great and simple serivce does exactly what I need. Made in Germany.

dynv6.com

If you have a Mikrotik router, you can use its built-in Dynamic DNS, and configure a CNAME on your domain name

For my server I bought a domain on loopia.se and pay for no other features than the domain name. On the Loopia website I then changed the DNS nameserver to Cloudflare and use a script to update the IP of my network. Cloudflare has some package you can install on Linux to update the IP but I never tried it.

Well, if you use DDNS I assume you have some kind of server behind that. I just self host a godns container. No need for any service except an DNS API. I use cloudflare. But my IP only changes rarely, so I can’t tell you how fast that setup propegates

I am using DuckDNS and it’s working perfectly for me. I use the DynDNS feature of my Fritz!Box to update my DuckDNS-IP. The documentation on their website is spot-on for me, even for my IPv6 and I never had any issues with DuckDNS.

What I like most about the service is the possibility to use subdomains like my-service.my-username.duckdns.org. I don’t know whether this is a commong feature or not.

When you had problems updating your IP Adresse did you consider that DNS information takes some time to propagate through the internet? I think it is not guaranteed that you can access a recently changed domain.

How did you test your DuckDNS entries?

DuckDNS was resolving slow as hell for me so I ended up picking up a cheap domain from Porkbun, they got API access and it seems most of the ddns tools support them too

I used nsupdate for years and it worked just fine. I remember it being down, one time only, for like five minutes. For a project that depends entirely on donations, the service and availability they provide are just awesome.

i am using freedns.afraid.org for over a decade now and problems occured less than 5 times over that period. all others i ever tried were worse over time.

My Domain registrar has a reverse DNS service included.

I’m currently using ipv64.net

Been using ddnss.de before that for some time, but they had some outages. No problems with ipv64 so far.

I’ve been using desec.io since it’s european, non profit and privacy oriented. Bring your own domain though. Works well, although my caddy plugin has problems getting certs sometimes. My pangolin instance never has any issues getting certs so might be caddy desec plugin specific.

Any DNS provider is good if they offer an API that lets you use PUT to modify DNS records. You can make a small bash script and crontab it. I also used DuckDNS for a while, and it worked fine.

This is a great question that is relevant for me this week. Been trying to set up a wireguard vpn and found I need a DDNS. Lots of good answers to look into in the comments. Thanks everyone.

DuckDNS has long enough latency (over 2000ms) where Google Assistant can’t connect. I moved to FreeDDNS and my Home Assistant issues went away.

Reference: community.home-assistant.io/t/…/140?page=7