neo290
Contributor
Contributor

Changing Hostname VCSA 6.7 Update 3b - doubled domain name

Hello,

After changing the host name in some places it has been doubled domain name.

Extra domain "cloud.local" has been added to FQDN.

d0pG6CU[1].png

pSXRGXq[1].png

Yes, I'm sure I set the correct hostname during the change Smiley Happy

root @ vcenter [~] # hostname
vcenter.cloud.local

root@vcenter [ ~ ]# /usr/lib/vmidentity/tools/scripts/lstool.py list --url http://localhost:7080/lookupservice/sdk --type vcenterserver 2> /dev/null |grep URL

                URL: https://vcenter.cloud.local:443/vcenter.cloud.local

                URL: https://vcenter.cloud.local:443/sdk

                URL: https://vcenter.cloud.local:443/sdk

                URL: https://vcenter.cloud.local:443/catalog/catalog.zip

                URL: https://vcenter.cloud.local:443/sdkTunnel

                URL: https://vcenter.cloud.local:443/sdk

fWQoqd3[1].png

NWTmY0p[1].png

I tried to restore the snapshot several times and change to other names, but a duplicate domain is always added.

My VCSA is also not connected to AD domain.

What should we do in order to fix duplicated domain name?

Thenx

0 Kudos
6 Replies
mc1903cae
Enthusiast
Enthusiast

Check the old Web Client and see if the domain name is duplicated in the same places. If they are NOT it’s most likely just a HTML5 client display issue.

If you have support there is no harm opening an SR and asking them to check the VCSA.

M

0 Kudos
neo290
Contributor
Contributor

The problem is on HTML5 and FLEX.

0 Kudos
mc1903cae
Enthusiast
Enthusiast

Probably best to open an SR if you can then.

What’s the history of this VCSA? What was the initial install version/build? How many times has it been upgraded and to what versions/build each time?

If you do get an answer from support please post the details here.

0 Kudos
neo290
Contributor
Contributor

Previously there was vCenter on Windows with a hostname without a domain and I think this is causing the problem in VCSA.

0 Kudos
neo290
Contributor
Contributor

I fixed this by modifying 12 records in LDAP.

0 Kudos
Takeaway
Contributor
Contributor

Can you explain what you did, we have the same issue.

0 Kudos