The problem I see is that in order to send a redirect you have to connect to the service and to connect to to an https service, the service has to present a certificate and the browser will complain if the CN on the cert does not match the full hostname of the URI. So the only way I see this working is if you had a service with a valid certificate of splunk.oldname.com responding on the IP where that FQDN points to which would then send a redirect to the splunk.oldname.com We have handled similar situations in the past by hosting certs on a load balancer and having it handle redirects, but essentially the flow (and cost of keeping old cert valid) is the same. One possible solution is a UCC/SAN certificate. ... View more