This way they could potentially gain control over your server.
The problem is that the folks at have the possibility of injecting malicious script into the result of "curl ". I went a bit further and made a more secure version of the script. This will update no-ip with a 1-hour interval. Use "crontab -e" command to edit your crontab. Now you need to use cron to schedule this update process. Then the no-ip client is used to update no-ip DNS to point to that IP. The script will use to figure out the IP of your cable modem. usr/local/bin/noip2 -i `cat /tmp/current_ip` Now the no-ip client is configured, we just need to give it the correct IP address.įor that we create a script somewhere, for example noipscript.sh: You need to enter your username, password, and select which of the hosts at no-ip you want to update. Note: You might see certain Linux guides telling. Using the update option tells apt to search your software repositories (everything listed in /etc/apt/sources.list) and take inventory of what Ubuntu package updates are available. Now, the no-ip client will ask you which hosts you want to update with the program. The Ubuntu update command is apt, or sometimes apt-get.
#Update no ip duc ubuntu install
Install also the no-ip client (more info at their help site): Script to install and configure no-ip client on Ubuntu/Debian.
dyndns -file-default -query-ipfile -provider dyndns -host To update account information to DDNS provider: dyndns -provider dyndns -loginProblem is, my server is in a LAN with an internal IP, while I need it to update with the IP address of my cable modem.ġ) no-ip - maybe the best free dynamic DNS?Ģ) - an AWESOME site for figuring out your IP in linuxįirst, have an account at ready, so sign in and create an account if you haven't done it yet. The option -file-default uses OSs default directory structure. All I needed was a script to do it for me, from inside the LAN of my home. I have a Linux server running, so my second option was to use that for updating the IP. No-ip is my favourite dynamic DNS service, and I was saddened by the fact that my new Cisco EPC3825 cable modem didn't support it.