...
On the other hand, you can create this situation intentionally for test purposes by adding names with the loopback or private addresses to the etc/hosts table on your desktop sandbox computer. Just remember the algorithm and you can figure out the testing tricks yourself.
This may seem complex, but in practice you will have a specific set of production and test machines and a sandbox development environment, you build a single configuration that specifies everything, test to make sure you haven't done anything dumb, and then you can create a single WAR file that automatically detects which environment it is running in and doesn't have to be changed when you move it across machines.
Autoconfigure
At Yale the names of DEV, TEST, and PROD machines follow a predictable pattern, and CAS clusters have only two machines. So production services asked that CAS automatically configure itself based on those conventions. If you have similar conventions and any Java coding expertise you can modify the autoconfiguration logic at the end of CushyClusterConfiguration Java source.
...