Arch Linux User Repository

Read and edit /etc/duckdns.d/default for more info on how to use the script!

rando, thanks for the suggestions!

@Nitroretro, would it make sense to add curl as a dependency? It's not part of the "base" ArchLinux package group, so it wouldn't hurt to list it explicitly ;)

Another small improvement: api6.ipify.org returns an IPv6 address only if the "api6.ipify.org" domain is resolved as IPv6. To force curl to do that, you can use the '-6' parameter like this: curl -6 -s "$IPV6_URL". For the IPv4 address retrieval, you can use the '-4' parameter like: curl -4 -s "$IPV4_URL"

Thanks for mantaining, your script has been really useful!

@Nitroretro now it works perfectly fine. Thanks again!

@inetbowser I have edited the units. Please tell me if you encounter any issues with them. Thank you for reporting the bug!

The original timer service didn't work properly on my machines. To be specific, after every reboot the timer service didn't activate (even after enabling it through systemctl enable duckdns.timer) and I had to restart it manually after every reboot.

This timer service fixed my problem:

[Unit]
Description=Update DuckDNS domain addresses every 10 minutes

[Timer]
OnCalendar=*:0/10
Unit=duckdns.service

[Install]
WantedBy=timers.target

PS: This may doesn't seem like a problem (because the timer will run every 10 minutes) but in duckdns.service it would be smart to add After=network-online.target, so that the script won't run before the network isn't online and I would add the service to multi-user.target.

So the duckdns.service would look something like this:

[Unit]
Description=Update DuckDNS domain addresses
After=network-online.target

[Service]
Type=oneshot
ExecStart=/usr/bin/duckdns

[Install]
WantedBy=multi-user.target

Read and edit /etc/duckdns.d/default for more info on how to use the script!