We’re going to need a way to automatically keep track of the IP address of the device as it potentially changes; as a fortuitous consequence, we’re going to be able to get an easy-to-remember URL in exchange.To do all this, we’re going to set up dynamic DNS using No-IP on Raspberry Pi.
First, you have to forward any ports you are intested in accessing from outside in your modem-router. Your ISP most likely will change your public IP every now and then, and also accessing by IP is harder because you have to remember it.
The solution to this is to use a dynamic DNS provider. Process 414, started as noip2, (version 2.1.9) Using configuration from /usr/local/etc/no-ip2Last IP Address set 0.0.0.0 Account [email protected] for: host mycloud.Updating every 30 minutes via /dev/eth0 with NAT enabled.
Now that we have a working own Cloud installation on our Raspberry Pi, we need a way to be able to remotely access the device from across the internet.
Knowing the IP address and forwarding the appropriate ports on the router is only part of the story: most residential ISPs will periodically change the external IP address of their customers for logistical reasons that we won’t get into here (it’s a matter of traditional infrastructure limitations and convenience for the ISP).
) Now, all you have to do is set up port forwarding on your router to point port 80 to the Raspberry Pi.
Every router’s instructions are going to be slightly different, so check your particular model’s documentation.
Since you can update hostnames in various ways, you can set up hosts to update differently all within the same Update client.
Once you click OK, an update will be sent with your new settings and if all goes well, you’ll get a good status like below.
If you get something other than a good status, click the Legend inside the client to see what it means.
You can quickly see which hosts are configured to be updated in your client by looking at the Host Status column to the right of each host.
This is a common warning as many internet service providers have not yet made IPv6 available to customers, and can be safely ignored so long as the hosts were updated successfully.