Noip duc not updating

The daemon now automatically start noip2 service and also succesfully updated the IP address. Sakura:-Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: n Vidia Ge Force GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSDMaking lemonade from lemons since 2015.

I initially having issue similar with developej, and I found that I need to add this: [Unit] Description=noip2 systemd-resolved.service [Service] Type=forking Timeout Start Sec=30 Exec Start=/usr/bin/noip2 -d -c /etc/no-ip2Restart=on-failure Restart Sec=30 [Install] Wanted Thank you for sharing that, ertehbasi, but two year old threads are not the best place to share this information -- the wiki is a much better place.

noip duc not updating-88noip duc not updating-29noip duc not updating-79

Like most things on your Arch system, it does not read your mind or try to configure things for you.See, this is something you should have mentioned in the first post.Product datasheet Upgrade Price Guarantee Compatible with Windows 10, 8.1, 8, 7, Vista and XP, 32 Bit / 64 Bit Editions New language versions: Chinese - Lithuanian - Japanese - Polski - Romanian - Spanish - Czech Update Star is compatible with Windows platforms.Update Star has been tested to meet all of the technical requirements to be compatible with Windows 10, 8.1, Windows 8, Windows 7, Windows Vista, Windows Server 2003, 2008, and Windows XP, 32 bit and 64 bit editions.Last_IP_Addr =, IP = I was getting those read-only errors too.

And it was apparently reading the config file when user nobody had no rights to read it.-edit-It starts as root, reads the config and changes to nobody.You can edit /usr/lib/systemd/system/noip2.service, append -d to the command there, run "systemctl reenable noip2; systemctl restart noip2" and see its debugging output in "systemctl status noip2" or "journalctl -u noip2". ⮀ systemctl status noip2.service noip2.service - No-IP Dynamic DNS Update Client Loaded: loaded (/usr/lib/systemd/system/noip2.service; enabled) Active: active (running) since Sat 2013-02-16 CET; 4min 50s ago Process: 3491 Exec Start=/usr/bin/noip2 -d -c /etc/no-ip2(code=exited, status=0/SUCCESS) Main PID: 3492 (noip2) CGroup: name=systemd:/system/noip2.service └─3492 /usr/bin/noip2 -d -c /etc/no-ip2well, i rerun noip2 configure, entered username and pw (like i did 3 times before), left the default time of 30 minutesthen i changed permissions before starting the service (of /etc/no-ip2.conf) to 644started the service and here is what the journal is saying:why do i get this last line today? also, what would be my course of action now - changing the permissions of no-ip2even though so many people use it with the same 644 permissions or maybe something else?then i left home with laptop, got on another wireless and here's the output of journalctl -u noip2-- Reboot -- Feb 23 wslap noip2[420]: v2.1.9 daemon started with NAT enabled Feb 23 wslap noip2[417]: Can't gethostbyname for dynupdate.Feb 23 wslap noip2[417]: Can't get our visible IP address from ip1.dynupdate.Feb 23 wslap noip2[417]: !Code refactored from first "quick and dirty" implementation to separate logical components.Hopefully easier to understand and to extend or refactor for your personal use Configurations renamed and rearranged for easier understanding e.g.ok, I came back home and it automatically updated the service is working, maybe that other wifi ap somehow blocked the service...anyway, I will mark this as solved.