FW: connect to build server that is dual homed/behind a firewall

I recently changed my build server to report to a central dashboard.
Self hosting the dash-board server on the build server can cause client
timeouts if the server is overloaded during a build.


The build server is behind a firewall.
It has an internal and external name.

The following machines exist.

Buildserver.local
Buildserver.internal
Dashboard.local
Client.local

Branch.Install is the name of cruisecontrol project.

All the machines are single homed machines on the same network except for
the build server.
The build server posts it's dashboard results to dashboard.local.
I view the dashboard results from client.local.


How can I configure the cruisecontrol server to select Buildserver.local
instead of Buildserver.internal for the port clients should connect back to
on to monitor the build output?


Loading the build results page from the dashboard server will tell the
client to load the build loop information from the build server.

It attempts to connect to the internal address of the buildserver from the
client.
The client attempts to connect to this address:
http://buildserver.internal:8000/mbean?objectname=CruiseControl%20Project:na
me=Branch.install

When it should connect to:
http://buildserver.local:8000/mbean?objectname=CruiseControl%20Project:name=
Branch.install 

I did find information on binding jmx to a dedicated address:
http://vafer.org/blog/20061010091658

Would this work?
Are there any other methods to use?



------------------------------------------------------------------------------