For years we've hosted our DNN sites in a fairly simple set up.  We have IIS running a few (say 10) sites, each running DNN with a single portal.

Now we've introduced a load balancer for failover, configured in front of two IIS servers, one active the other passive.  I've just upgraded each DNN instance to version 5.06.02.

The load balancer has 10x public IP's, and the two IIS servers each have a single private IP.

The load balancer forwards incoming requests to IIS on a particular port (say 8080), I tried host-headers but IIS didn't pick that up from the incoming request -- I thought the LB would keep the host header in tact, but maybe I'm wrong (going to sniff this out next week).

To get DNN to respond, I've added the alias to the portalalias table.  I've had to add the private IP and port (say 192.10.10.10:8080).  UsePortNumber in the web.config is set to true.

And here is the problem.  When i surf to the external host name, DNN comes up (so the request gets through) but all the links have the private IP address and port - presumably because that's the address the LB is coming in to.

I must be doing somethign wrong.  How can I tell DNN to serve up either a) relative URL's or b) the correct external host (maybe a default alias).  I would really appreciate someone pointing me in the right direction.  Any info at all would be great.  Today, Google has not been my friend.

/Simon