How To Set Up And Use DigitalOcean Private Networking Introduction DigitalOcean now offers shared private networking in NYC2. All new droplets created in NYC2 have the option of using private networking; it can be activated by choosing the checkbox called "Private Networking" in the settings section of the droplet create page. If you already have a server in NYC2 set up without private networking, you can refer to this tutorial, which covers how to enable private networking on existing droplets. Droplets that have the private networking enabled are then able to communicate with other droplets that have that interface as well. The shared private networking on DigitalOcean droplets is represented by a second interface on each server that has no internet access. This article will cover finding a droplet's private network address, transferring a file via the private network, and updating the /etc/hosts file. Step One — Create Droplets with Private Networking At this point, in order to take advantage of the private networking, you do need to create new servers in NYC2. In this tutorial, we will refer to two droplets: pnv1 (111.222.333.444) and pnv2 (123.456.78.90). Go ahead and create both, enabling the Private Networking on the droplet create page. Step Two — Find your Private Network Address Once both servers have been spun up, go ahead and log into one of them: pnv2: ssh [email protected] Once you are logged into the server, you can see the private address with ifconfig. The output of the command is displayed below: ifconfig eth0 Link encap:Ethernet HWaddr 04:01:06:a7:6f:01 inet addr:123.456.78.90 Bcast:123.456.78.255 Mask:255.255.255.0 inet6 addr:…