The log file shows that noip2 was indeed stopped:
Preparando para reemplazar noip2 2.1.9-3 (usando .../noip2_2.1.9-3_amd64.deb)
...
* Stopping No-IP.com dynamic address update noip2
...done.
The actual problem here seems to be that the noip2 executable generates
its configuration file in
Patch is available.
See Debian bug #527293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527293
** Bug watch added: Debian Bug tracker #527293
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527293
--
firefox w/ mplayer plugin crashes on .mov file
https://bugs.launchpad.net/bugs/360222
Fixed in Debian since 2.1.7-10
--
noip2 does not start at boot when installed from apt on 8.10 server
https://bugs.launchpad.net/bugs/322371
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Workaround - run the following in a cron job every 30 days (replace X
and no-ip.com with the correct host and domain):
/usr/bin/wget -q -O - 'http://www.no-ip.com/hostactive.php?host=Xdomain
=no-ip.com'
--
ip not being updated and expiring
https://bugs.launchpad.net/bugs/274479
You received
Has your ISP, by any chance, assigned you a static IP?
--
ip not being updated and expiring
https://bugs.launchpad.net/bugs/274479
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Well, it seems that their policy is different [1].
[1] http://www.no-ip.com/support/faq/EN/general/hosts-pending-
deletion.html
--
ip not being updated and expiring
https://bugs.launchpad.net/bugs/274479
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It does not seem to be a client limitation: the client can't update the
host when the IP has not changed, because, apparently, the no-ip server
does not allow it. That's at least how I read it.
The no-ip free service is limited this way.
Silly? maybe. Bug? hardly. It looks and smells deliberate.
