adding VCSA to domain renames the dns suffix to the domain.

The other day, I had a customer having all management applications on a different DNS suffux as that of the domain.

Ie: Domain :
Management host’s: on mgmt.local

on the customer’s setup, the VCSA was deployed with an FQDN VCSA.MGMT.local However, when the appliance was added to domain, the VCSA renames itself to


Apparently the likewise scripts on VCSA is set to rename the appliance to the domain suffix. This might cause all sort of strange behaviour/PNID mismatches on normal functionality.


In order to sort this/set this right, we  wanna invoke the domain join script ignoring  the hostname.

Syntax: /opt/likewise/bin/domainjoin-cli join –disable hostname domain_name domain_user


root@vcsa [ ~ ]# /opt/likewise/bin/domainjoin-cli join –disable hostname nik
Joining to AD Domain:
With Computer DNS Name: vcsa.mgmt.local


notice that the script acknowledges that it is going to join to join AD with the computer name vcsa.mgmt.local. this is precisely what we want.

Related Posts
%d bloggers like this: