Systemd Service file for no-ip.com dynamic ip updater

noip2.service

# Simple No-ip.com Dynamic DNS Updater
#
# By Nathan Giesbrecht (http://nathangiesbrecht.com)
#
# 1) Install binary as described in no-ip.com's source file (assuming results in /usr/local/bin)
# 2) Run sudo /usr/local/bin/noip2 -C to generate configuration file
# 3) Copy this file noip2.service to /etc/systemd/system/
# 4) Execute `sudo systemctl daemon-reload`
# 5) Execute `sudo systemctl enable noip2`
# 6) Execute `sudo systemctl start noip2`
#
# systemd supports lots of fancy features, look here (and linked docs) for a full list:
#   http://www.freedesktop.org/software/systemd/man/systemd.exec.html

[Unit]
Description=No-ip.com dynamic IP address updater
After=network.target
After=syslog.target

[Install]
WantedBy=multi-user.target
Alias=noip.service

[Service]
# Start main service
ExecStart=/usr/local/bin/noip2
Restart=always
Type=forking

Author of noip-duc v3 here. Great to see the interest!

I like the restart changes, I'll get them incorporated into the package. In 3.0.0-beta.7 (2023-08-08) it will no longer exit if it cannot resolve hostnames for checking the current IP during start up.

As for the configuration, a better way to handle it so that you don't need to put your password in the unit file it to use environment variables and the systemd Service setting EnvironmentFile. Nearly every command line option has an equivalent env var. You can find them all in the help as well as the README.md.

/etc/noip-duc.env

NOIP_USERNAME=example-username
NOIP_PASSWORD=eXamPle-Pas5w0r&
NOIP_HOSTNAMES=h1.example.com,h2.example.com

Addition to unit file

[Service]
EnvironmentFile=/etc/noip-duc.env

By using EnvironmentFile= instead of EnvironmentFile=- the service will not start unless the file exists, in that way the service will not take any resources unless configured.

Please send in other suggestions or recommendations! I'm so happy to see the interest here!

I've created this project ... if someone it's interested, more than welcome! Cheers! https://github.com/felipealfonsog/NoIP-Manager

Thanks, @felipealfonsog! That is very cool.

Hello, how do I know the version that I have installed by NOIP? NOIP.SERVICE -V / NOIP2 -V, how would it be? thank you!

@tute123456 If you have the noip2 binary then you are running the old 2.x client. In the new 3.x client the binary is called noip-duc. Try which noip2 and which noip-duc to determine which one exists.

If you're on an apt-based system like Debian or Ubuntu you can find the version with dpkg -l 'noip*'. On Fedora and possibly other rpm-based distributions the command may be like dnf list installed | grep -i noip. I don't have a rpm-based system handy to verify.

@tute123456 If you have the noip2 binary then you are running the old 2.x client. In the new 3.x client the binary is called noip-duc. Try which noip2 and which noip-duc to determine which one exists.

If you're on an apt-based system like Debian or Ubuntu you can find the version with dpkg -l 'noip*'. On Fedora and possibly other rpm-based distributions the command may be like dnf list installed | grep -i noip. I don't have a rpm-based system handy to verify.

Thank you, you could pass me a link for the installation of version 3.3, or if possible a guide to erase the old 2.x and install the new one, thank you very much!