We orginally setup the vcenter 6.7 server under its IP as there was no ability for a Domain name, everything worked fine. just last month we ran into some SSL Cert issues and changed the name to a internal domain name - serverx.domainx.com - regenerated the SSL and got things back up. Now we come to find out we need to use a real internal domain name as not everyone in the company can access the vcenter - so we changed the FQDN again, to newserverx.newdomainx.com but now the services won't start. We rebuilt the SSL certs and that completed just fine but the services will not start up and it has something to do with the SSO - while debuging this we are noticing the SSO has mulitple domains attached to it .. if we run:
./vdcrepadmin -f showservers -h lexicon.xsubdomain.xdomain.com -u administrator
--------------------------------------------------
cn=10.10.10.10,cn=Servers,cn=default-site,cn=Sites,cn=Configuration,dc=vsphere,dc=local
cn=photon-machine.olddomainname.com,cn=Servers,cn=default-site,cn=Sites,cn=Configuration,dc=vsphere,dc=local
cn=photon-machine,cn=Servers,cn=default-site,cn=Sites,cn=Configuration,dc=vsphere,dc=local
cn=lexicon.xsubdomain.xdomain.com,cn=Servers,cn=default-site,cn=Sites,cn=Configuration,dc=vsphere,dc=local
the server seems to be retaining all the names we had changed it to at one point. We have tried the lsdoctor tool but it fails to run with an error
--------------
socket.gaierror: [Errno -2] Name or service not known
It does show the Certs are mismatched but it throws that error with the --trustfix option. It also throws that error when we try and rebuild (with -r)
Does anyone know how we can clean up the old names so it just has lexicon.xsubdomain.xdomain.com ?
Thank you!
