I have a POC Lab setup for SharePoint/OfficeWebApps with SSL offloading. I am using IIS reverse proxy for my SSL offloader. Most systems can connect to SharePoint and OWA through the Loadbalancer and create documents as desired. The configuration is as follows:
DNS points:
sharepoint.contoso.com to the reverse proxy address that handles sharepoint.
owa.contoso.com to the reverse proxy address that handles owa.
My OfficeWebApps farm uses an internal and external url of
https://owa.contoso.com and uses ssloffload.
My SPWOPIBinging connects to owa.sharepoint.com (through the reverse proxy) and is configured with the external-https zone.
The name of the OWA server is nyc-owa1.contoso.com.
The issue is as follows:
If I flush my dnscache before connecting to
https://sharepoint.contoso.com, and then use OWA in sharepoint, my client DNS cache will list sharepoint.contoso.com, owa.contoso.com AND nyc-owa1.contoso.com!
Where is is getting the name of the actual owa server?
If I simulate an Internet client that cannot resolve the internal name nyc-owa1.contoso.com, but only the public names of sharepoint.contoso.com and owa.contoso.com, the client cannot successfully edit a new or existing file with OWA, the browser hangs with Java errors ('SYS' is undefined etc.)
When I add either the real IP address of the server nyc-owa1.contoso.com OR the reverse proxy address for nyc-owa1.contoso.com to a hosts file, the client works normally.
I would like to know how the client is getting the OWA server's name and how to control that behavior.
Thanks for reading this!!
-Scott