We have multiple FQDN pointing to our own Connect server. Lets say we have configured first.ourcompany.com as our Connect Host FQDN and we also have an alias second.ourcompany.com pointing to the same server's IP address. When user browses to second.ourcompany.com the visible URL in browser changes to first.ourcompany.com. This is totally cool and we want it to work like that.
The problem is that we have linked some public videos and meeting recordings all over the place. We have numerous links such as http://first.ourcompany.com/p75947479/ and they work flawlessly as is. Now we would like to change our visible Connect FQDN into second.ourcompany.com, but when browsing to URL http://second.ourcompany.com/p75947479/ Connect prints out "not found" error page and says that the resource cannot be found.
Is there anything we could do in order to make both links work properly or should we just accept the fact that all those links will break if we change Connect Host FQDN?