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

Thanks, this is exactly what I needed!

Thank you!

Thanks

Thx!

👍

Tks a lot!

Thank you!

Thank you! It's perfect: short, concise and to the target!
It worked flawlessly in a Raspeberry Pi 3 with opensuse Leap 43.2

Great work 👍 👍 👍

Thanks

Many thanks!

Thanks

Thank you! :)
Works perfectly on rpi B+ under Raspbian!

https://bugzilla.redhat.com/show_bug.cgi?id=1431368
Can't gethostbyname for dynupdate.no-ip.com
Can't get our visible IP address from ip1.dynupdate.no-ip.com

for those that have this error on boot, just change replace:
[Unit]
Description=No-ip.com dynamic IP address updater
Wants=network-online.target
After=network-online.target

Thank you for snippets :)

Very awesome!!!! Thank you!!!!

Don't forget to do a "sudo systemctl enable noip2.service" to enable this and create the proper symlinks. Then it will run on reboot.

Thanks! Wrote this myself WAY too many times... but this one is more reliable, somehow.

Thanks!

Thanks! Couldn't get mine to work...

Thanks! Works like a charm :)

Perfect! Worked right out of the box for Ubuntu 18.04 LTS. Thanks for sharing!

Awesome

Thanks!

Thanks dude, that's great for a lazy ass like me :-)
Awesome!

Thank you!

👍 👍

Thank you very much. It saved me several hours as I've ever remember them.

Thanks!

So I think there is a problem. I don't think it re-runs this periodically to update network changes (at least it does not on my machine). Is there a change we can make to do this?

I figured it out. It turns out the noip2 binary defaults to updating only every 30 DAYS (not minutes). Oddly, you have to do this to change the config file default:

pkill noip2 # stop running daemon
/usr/local/bin/noip2 -U 30 # rewrite /usr/local/etc/no-ip2.conf files with new data
/usr/local/bin/noip2 # restart actual daemon; previous step does NOT do this

I think the issue here is that when we go to the no-ip2 website we see that our ip hasn't updated for longer than the interval we set.

This happens because, with default values, noip2 only sends updates when the ip changes.

If you want to change this default behavior, you'll want to change two values in noip2.c

• change the line #define FORCE_UPDATE 0 to #define FORCE_UPDATE 1
• change the line #define FORCE_INTERVAL (1440 * 30) to be the time period in minutes that you want to force an update. for example if we want to update every 15 minutes we should change it to #define FORCE_INTERVAL(15)

Once you have done this rerun make clean install.

Can anyone help me. When I check status, I always get :

   Loaded: loaded (/etc/systemd/system/noip2.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2019-06-21 12:59:07 BST; 10s ago
  Process: 7405 ExecStart=/usr/local/bin/noip2 (code=exited, status=0/SUCCESS)
 Main PID: 7406 (code=exited, status=255)

Jun 21 12:59:07 raspberrypi systemd[1]: noip2.service: Failed with result 'exit-code'.
Jun 21 12:59:07 raspberrypi systemd[1]: noip2.service: Service hold-off time over, scheduling restart.
Jun 21 12:59:07 raspberrypi systemd[1]: Stopped No-ip.com dynamic IP address updater.
Jun 21 12:59:07 raspberrypi systemd[1]: noip2.service: Start request repeated too quickly.
Jun 21 12:59:07 raspberrypi systemd[1]: Failed to start No-ip.com dynamic IP address updater.
Jun 21 12:59:07 raspberrypi systemd[1]: noip2.service: Unit entered failed state.
Jun 21 12:59:07 raspberrypi systemd[1]: noip2.service: Failed with result 'exit-code'.

What flags are you passing to the executable?

Thanks!

Many thanks, Nathan! You have done the trick :-) It works like a charm...

In between steps 3 and 4 you are missing a step.

See missing step 4) below:

# 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`

In between steps 3 and 4 you are missing a step.

See missing step 4) below:

# 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`

Thanks!

Thanks! Why noip.com not reffer to here!?!? Just envy???

Great job!

Works great!

Thanks for the clean & simple solution!

Why the service run as "nobody"? How to make it run as "root"?

root 5409 0.0 0.0 21224 2748 ? S 01:33 0:00 /lib/systemd/systemd-udevd
root 5410 0.0 0.0 21224 2744 ? S 01:33 0:00 /lib/systemd/systemd-udevd
root 5411 0.0 0.0 21224 2744 ? S 01:33 0:00 /lib/systemd/systemd-udevd
nobody 5412 0.0 0.0 4832 1956 ? Ss 01:33 0:00 /usr/local/bin/noip2
root 5413 0.0 0.0 21224 2744 ? S 01:33 0:00 /lib/systemd/systemd-udevd
root 5414 0.0 0.0 21224 2744 ? S 01:33 0:00 /lib/systemd/systemd-udevd

Why the service run as "nobody"? How to make it run as "root"?

root 5409 0.0 0.0 21224 2748 ? S 01:33 0:00 /lib/systemd/systemd-udevd
root 5410 0.0 0.0 21224 2744 ? S 01:33 0:00 /lib/systemd/systemd-udevd
root 5411 0.0 0.0 21224 2744 ? S 01:33 0:00 /lib/systemd/systemd-udevd
nobody 5412 0.0 0.0 4832 1956 ? Ss 01:33 0:00 /usr/local/bin/noip2
root 5413 0.0 0.0 21224 2744 ? S 01:33 0:00 /lib/systemd/systemd-udevd
root 5414 0.0 0.0 21224 2744 ? S 01:33 0:00 /lib/systemd/systemd-udevd

I don't think it needs to run as a privileged user as it's not updating anything on your own system. But if you're having problems I'd suggest checking out the SystemD service file docs https://www.freedesktop.org/software/systemd/man/systemd.exec.html

Thanks!

Thank you, folks!

Thank you. It's work fine.

yessss thanks

Very good. Thanks.

Awesome!! I would like to add, for anyone running a VPN on boot as well (using OpenVPN), perhaps you want the noip2 service to wait until VPN is connected before updating address. In this case just change the Requires and After:

[Unit]
Description=No-ip.com dynamic IP address updater
Requires=sys-devices-virtual-net-tun0.device
After=sys-devices-virtual-net-tun0.device

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

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

very good! thnx

I am getting error here.

➜  system sudo systemctl status noip2
● noip2.service - No-ip.com dynamic IP address updater
     Loaded: loaded (/etc/systemd/system/noip2.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2020-07-03 21:42:24 +08; 20s ago
    Process: 23625 ExecStart=/usr/local/bin/noip2 (code=exited, status=0/SUCCESS)
   Main PID: 23626 (code=exited, status=255/EXCEPTION)

Jul 03 21:42:24 pop-os systemd[1]: noip2.service: Scheduled restart job, restart counter is at 5.
Jul 03 21:42:24 pop-os systemd[1]: Stopped No-ip.com dynamic IP address updater.
Jul 03 21:42:24 pop-os systemd[1]: noip2.service: Start request repeated too quickly.
Jul 03 21:42:24 pop-os systemd[1]: noip2.service: Failed with result 'exit-code'.
Jul 03 21:42:24 pop-os systemd[1]: Failed to start No-ip.com dynamic IP address updater.

what I did wrong?

Same issue here.

Hover running:
sudo noip2 -S
Output:

1 noip2 process active.

Process 1009, started as noip2, (version 2.1.9)
Using configuration from /usr/local/etc/no-ip2.conf
Last IP Address set 0.0.0.0
Account ***********@gmail.com
configured for:
	host  **********.com
Updating every 5 minutes via /dev/wlx281878338e41 with NAT enabled.

So it might be still working fine. Not sure.

You are the fucking Best¡ Greetings from Argentina¡

https://bugzilla.redhat.com/show_bug.cgi?id=1431368
Can't gethostbyname for dynupdate.no-ip.com
Can't get our visible IP address from ip1.dynupdate.no-ip.com

for those that have this error on boot, just change replace:
[Unit]
Description=No-ip.com dynamic IP address updater
Wants=network-online.target
After=network-online.target

Thank you for snippets :)

I tried to do it on my Raspberry Pi 3B running Raspbian Buster to avoid setting 0.0.0.0 as my IP address but it seems not to be working...

A temporary fix I did was calling the following on my sudo's crontab:

@reboot sh -c "sudo noip2 -i $(curl -sS ifconfig.me)"

Hi

I'm following along with this tutorial:
https://www.youtube.com/watch?v=HTLwGTkBFy4&list=PLjwDNSlPlIIunYlhIRuftmmPmMZlze6WJ&index=13
4mins30seconds

Im getting the following when I run
sudo systemctl enable noip2
error:
/etc/systemd/system$ sudo systemctl enable noip2 Failed to execute operation: No such file or directory

I noticed there is an extra step here to do with the daemon which Ive done but am not really getting it an was hoping it would just work.

Anyone got any ideas, or know how to check if its running properly? I left it at the default 30
Cheers

Answer:
I got this fixed by killing the process with the -K switch(kill proc id didnt do anything as it auto restarted each time) in the readme in noip folder(Dont know why they didnt just put it on the website) and then doing the daemon step later.

Not sure if its 100% right yet because I have to wait for the name servers to replicate around, but Im passed the roadblock of not being able to get tthe service runnign and the restart launch not working. Hope someone else gets

Hi,

I experience a different behavior:
When run from command line noip2 forks and stays running as a daemon. I can see it using 'ps aux'.
When run as a systemd service, is does not fork and using type=forking does not work for me.
I had to switch to type=simple. But now noip2 exits after updating the IP.
It seems it is expecting to be run as a systemd timer.
How can noip2 behave so differently depending on how you call it...?

Nice job it works and helps by just copy/pasting 👍

Thank you works perfectly. cheers

Thank you very much

I was so close, but no cigars..... now my noip2.service purrs like a kitten. Thank you!

I was having this error as well in a Raspbian installation:

Can't gethostbyname for dynupdate.no-ip.com
Can't get our visible IP address from ip1.dynupdate.no-ip.com

Found a workaround, just add to noip2.service file:

[Service]
ExecStartPre=/bin/sh -c 'until ping -c1 google.com; do sleep 1; done;'

After rebooting, now it works. systemctl status noip2.service:

Dec 15 02:51:35 msdos sh[674]: ping: google.com: Temporary failure in name resolution
Dec 15 02:51:36 msdos sh[674]: ping: google.com: Temporary failure in name resolution
Dec 15 02:51:37 msdos sh[674]: PING google.com() 56 data bytes
Dec 15 02:51:37 msdos sh[674]: 64 bytes from (): icmp_seq=1 ttl=119 time=10.7 ms
Dec 15 02:51:37 msdos sh[674]: --- google.com ping statistics ---
Dec 15 02:51:37 msdos sh[674]: 1 packets transmitted, 1 received, 0% packet loss, time 0ms
Dec 15 02:51:37 msdos sh[674]: rtt min/avg/max/mdev = 
Dec 15 02:51:37 msdos systemd[1]: Started No-ip.com dynamic IP address updater.
Dec 15 02:51:37 msdos noip2[1030]: v2.1.9 daemon started with NAT enabled
Dec 15 02:51:41 msdos noip2[1030]: mydns.ddns.net was already set to xxx.xxx.xxx.xxx

Not exactly "pretty" but with all due respect, I've spent three hours using noip2.service files from the whole internet, from centos to slackware to arch linux with no solution.

thank you so much
Wants=network-online.target
After=network-online.target
two lines fixed my problem

Works perfectly wit TurnKey GNU/Linux 16.0 (Debian 10/Buster). Thank you.

On RHEL, where SELinux is enabled, you might need to run:

restorecon /etc/systemd/system/noip2.service