In the previous post regarding Instance.com’s virtual networking features you can see how you can manage single or multiple instances using a single IP address. Sometimes you just can’t change the port a service runs on which is typical of public web servers where you can’t provide a unique URL such as http://my.developement.site:8080 or for mail servers, Name Servers, and any other service where the public client expects a standard port. Given this requirement the Instance.com product allows you to acquire additional IP addresses as needed to meet these requirements.
In this example you will see how to use unique public IP addresses for each instance to provide global services to your users.
In this example you will want to acquire an additional IP address to create the additional port-forward for the public service (HTTP – Port 80)
You can then choose the new address added to your account and proceed to create the port-forward as before.
At this point you should have two HTTP servers listening on the standard port 80 each with their own unique IP address.
The next configuration we will explain will be direct public IP addresses, the most simple networking configuration possible and then a combination of many to create a power network infrastructure from which to run your applications.