FQDN Management and Allocation
On this topic
On the first time installation of 3CX V15 the license key will be bound to the freely chosen FQDN by the administrator. Therefore, the administrator would need to select the FQDN carefully during the first time installation.
3CX Provided Domain
Starting with V15, customers with valid maintenance can receive an external DNS entry within certain 3CX top level domains - free of charge. On top of those managed FQDN - users will also be supplied with a state of the art widely trusted SSL certificate issued by Let’s Encrypt.
Keep in mind, once you have deviced on the userpart of the FQDN (userpart.hostpart.tld), this is bound to the license key. For evaluation tests with free issued “PBX Edition Keys” it is recommended not to chose your own company name, as it will prevent this FQDN from being used by your main production license key.
While the user part of the FQDN is bound to the license key, the top level domain can be altered at any time. Therfore it is possible to change from company.3cx.eu to company.3cx.us. Also, the userpart of the FQDN must be unique across all 3CX top level domains to ensure the business integrity. The allocation is on a first come first serve basis. So reserve your FQDN today by switching to v15.
Note: 3CX reserves the right to revoke any FQDN which might breach another company’s trademark rights, being of an offensive or racistic nature, without any warning. Also users have no right to claim an FQDN which is already in use.
Customer Own Domain
In case the installation is installed on a customer owned domain also a valid public trusted certificate covering the 3CX installation must be present during installation. No Let’s Encrypt Cert can be issued in this case by 3CX.
Also, in this case the license key will be bound to the customer FQDN. However the rules for binding FQDNs are slightly different. Assuming the installation is performed for company.mybusiness.com. The prerequisite for this is that the domain companymybusiness.3cx.* is not already taken. This FQDN is needed for the creation of the corresponding web meeting access point.
Altering the FQDN
In the case that a license key is free from an already mapped FQDN in order to assign it to a new FQDN, this must be performed via the ERP (https://erp.3cx.com) by releasing the domain back into the pool.
Every 3CX license key has a corresponding unique user allowing you login to https://erp.3cx.com. This information is emailed to the registered user of the product upon registration or sign up for the PBX Edition.
If you can not remember the password, you can reset it from the same place (https://erp.3cx.com). An email with further instructions is send to the product owner.
Once successfully logged in you will be presented with the status of your license key. You may release the key from here. In case you were not sure what you had selected previously you can see the information in the FQDN tab.
Login to the 3CX ERP System (https://erp.3cx.com) with your partner account details.If you can not remember the password, you can reset it from the same place (https://erp.3cx.com). An email with further instructions is sent to the partner account owner.
Once successfully logged in navigate to Dashboard > NFR Keys.
From here you can review all your keys, where they are bound to and unbind them if needed.
- First time installation binds the FQDN to the key
- In case the chosen FQDN is already in use:
- Error creating FQDN: FQDN already in use. Please choose another one
- Solution: Pick another free FQDN
- Subcentral installation of the same key required to enter the same FQDN
- In case the entered FQDN does not match:
- Error creating FQDN: License key already bound to another FQDN.
- Solution A: Login to the erp.3cx.com and check what the binded FQDN is
- Solution B: Login to the erp.3cx.com and release the FQDN to choose a new one