For many projects with the small computer, it’s either useful or necessary to provide Raspberry Pi with a static IP address.
But before we talk more specifically about the use of such a static IP address with Raspberry Pi, we’ll first outline the differences between addressing a computer in a private (local) network or on the publicly accessible internet.
Since IP addresses in a private network are individually assigned by the DHCP and the coupling of devices to an IP address is only valid within your local network, here we’re talking about private IP addresses.
In the default settings, Raspberry Pi also receives its IP address via the DHCP server.
Every time, as soon as your IP address changes, a program redirects the new address to the domain name and makes it permanently available on the internet.
Now if you link a server on Raspberry Pi with the domain name, it’s permanently accessible online. Before you decide on one for yourself, you should first test which DDNS providers your router supports, and whether it supports any at all.
This changes the public IP address with which the Raspberry Pi server can be reached.
If you want to set up your Raspberry Pi as an own Cloud server or in another server form, the following problem occurs: As soon as the server receives a new IP address, it can only be traced in the LAN.
The single-board computer Raspberry Pi always needs a static IP address if you want to access it with other devices over a long period of time.
This refers to the private IP address of the Raspberry IP that is located by a computer within the local network as well as the public IP address of the network via which the Raspberry Pi is accessible on the internet (for example, if it’s being used as a server).