We created an internal interface VIP name for the edge pool that is not compliant with public CA specifications from RFC 5280. Therefore a cert can not be generated using this name. How do I go about changing the FQDN of the internal Edge pool to a compliant one for the public CA?
The topology is published so I can not change the name of the edge pool FQDN so I figured I could delete the existing pool after dis-associating it with the front end pool, then create new one. This generates an ominous error that the edge pool serves as a federation route but I answered yes anyway.
When I try to add a new server in the "Define the computers in the pool" screen and the topology builder generates an error that the FQDN I input is already in use in the published topology. Catch 22.
I was thinking that I might be able to delete the edge pool, publish the topology without it. Then add the new edge pool and publish that. Server names haven't changed, just the pool FQDN.
Thoughts?