The situation:
There is a VRA7 built with a DNS domain name of domain.local in an isolated environment.
The the expectation that once built, all that was needed was the IP address of the VRA7 to facilitate end user access to the catalog for VM creation.
The VRA7 appliance thinks it's name is vra.domain.local.
The company has since assigned a FQDN to the VRA7 appliance, vra.company.com.
The end user experience:
A request is made via web browser to the VRA via it's FQDN of vra.company.com.
This resolves to the proper IP of the VRA and reaches the web engine and receives an HTTP redirect code with a URL that contains the machine name of vra.domain.local.
This fails since this is not a domain used within the company.
Additional information:
There is no traction to deploy a bogus domain within the company for domain.local.
It would appear that the VRA7 appliance hard codes the initial appliance name into the web server database tables.
It would appear that the VRA7 appliance does not have relative HTTP links, but hard coded FULL links.
Actions already attempted:
Changing the domain name and hostname of the VRA appliance through the appliance management GUI.
The question:
Where does one go to change the vra.domain.local part of that hard coded URL in the redirect (and assumed elsewhere within the VRA7 user GUI) without having to tear it down and rebuild it entirely?
With regards and thanks,
-dj