Hi Fariborz, Instance FQDN is generate from the VM name when you deploy it (becomes hostname) and the network domain set on the network to which a VM is joined. So: In case of Shared or Isolated Network, you have an option to set "network domain" when creating the network. In case of VPC, you have the option to set "DNS domain for Guest Networks" as seen in new VPC wizard in GUI.
Domain name, if not specified is inherited from the global setting guest.domain.suffix (if not mistaken). You can always hack the DB and change network/VPC domain name (for specific network) in appropriate tables (just FYI, but don't attempt without DB backup) and restarting that network/VPC with Clean Up. Hope that helps, Andrija andrija.pa...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue -----Original Message----- From: Fariborz Navidan <mdvlinqu...@gmail.com> Sent: 25 April 2019 15:07 To: users@cloudstack.apache.org Subject: Cannot create instance with FQDN hello folks, When creating a new instance, it does not aceept dots to use in instance name and there seems to be no way to explicitly set hostname for VM. It means hostnames cannot be a FQDN in ACS. How do you deal with this? Is there any setting to allow dots in instance name or assign hostnames explicitly and not to use VM name as hostname? Kind Regards
