Vanity/Custom URL configurations

[kristenmkar]

Good afternoon! 

I just have a few questions regarding the setup of an alternate URL/DNS Entry.  We worked with our Boundary team to develop a new DNS Entry/URL for our instance utilizing an IP address. We didn't notice any issues until we started seeing many of the notifications using the base URL (which makes sense because the sys_prop "glide.servlet.uri" still reflects the base instance URL).  I also noticed that many of the Share/direct links (i.e. the VTB "Share" Link) reflect the base instance URL, as well as the "Edit" button in a record that allows you to switch application scopes to edit (also navigates to the base URL). 

My first thought was that we needed to install the Custom URL Plugin and configure that - however, I realized that our DNS Entry is an A record and not a CNAME record.   In order to add a CNAME we would have to create a new DNS record - our A record points the domain directly to an IP address which is what was originally suggested to us  (vs a CNAME record pointing to another domain name).  We can still change this if needed (I believe), but wondering if that will actually fix the issues with the links/email notifications.  Is there a sys_prop or something else I should update?  I know I cannot manually change the glide.servlet.uri, but recognize this is referenced in most configurations. Otherwise everything else is working fine in terms of logging into the app, etc. 

Thank you!

[kristenmkar · Accepted solution]

I was able to figure this out if anyone runs into this problem! You will need to add a new system property called glide.proxy.host with the value of your alternate site. This will automatically update the glide.servlet.uri property the next time the instance node restarts.