Greetings!

I’m not sure if this is the best path, because I’m not completely following on the use case, but I found an article that may be helpful:
https://www.transip.eu/knowledgebase/entry/156-configuring-internal-ip-addresses-linux-vps/

Since we use 10. ranges for our private networking, I recommend using something like 192.168 ranges to avoid any future conflicts.

In my experience when anyone hosts websites on individual IP addresses on the system, they use a container setup that generally manages internal IPs for them and thus may make it inappropriate to use the technique I linked. If not using containers, it may make more sense to simply use virtual hosts as they were intended to be used - by name direct to content. If you have an individual service listening for each website on it’s own internal IP, you’re likely wasting resources by creating multiple instances of an application that is capable of handling all requests under one instance.

Jarland