Okay here is our scenario:
Loadmaster with two legs - Internet on 172.16.x.x, Real servers in 10.x.x.x
OOS server on 10.x.x.100
OOS server is part of a domain call foo so has a FQDN of oos.foo.domain.com
We have given it a simple name (and extra A record in DNS) of oos.domain.com in both internal and external (public) DNS.
We have set the URL on OOS to oos.domain.com
If internally we browse directly to http://oos.domain.com/hosting/discovery then the xml shows us oos.domain.com as expected.
If internally we browse directly to http://10.x.x.100/hosting/discovery then the xml shows us oos.foo.domain.com presumably because a reverse DNS lookup has occurred.
We configure Loadmaster to offload the SSL and have a redirect in place. I am using 126.96.36.199 with the Lync Office Web App Servers 2013 template.
Sharepoint is set to serve HTTP True with SSLOffloaded to True
If we EXTERNALLY browse via Loadmaster to https://oos.domain.com/hosting/discovery the xml shows us oos.foo.domain.com as if we are browsing via ip address.
I note that the Real Servers entry shows that the IP address resolves to the FQDN oos.foo.domain.com so tried adding a hosts file entry via the webadmin. This updated the Real Servers display to show oos.domain.com instead. It did not change the resulting xml though.
We are trying to use OOS with our Sharepoint but this is failing with the SP generated links (which are http - which are then redirected). We believe this is due to the above.
Anyone seen and solved this with OOS or Office Web Apps ?