3CX FQDN Management and Allocation - FAQs
Zero Admin
With the new Dashboard
Bulletproof Security
With SSL certs and NGINX
Install on $150 Appliance
Intel MiniPC architecture
New, Intuitive Windows Client
More themes, more UC
More CRM Integrations
Scripting Interface to add your own
Improved Integrated Web Conferencing
iOS and Android apps included
Personal Click2Meet URLs

FQDN Management and Allocation

FQDN Management and Allocation

On this topic

FQDN Management and Allocation

Introduction

3CX Provided Domain

Customer Own Domain

Altering the FQDN

Summary

See also

Introduction

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. The definition below require SP4 installers and first time FQDN setup.

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) and a domain suffix (userpart.hostpart.tld), this combination is bound to the license key. Every FQDN will also create a WebMeeting URL based on the following syntax:

  • userpart.hostpart.tld -> userpart-tld.3cx.net
  • Regular domains:
    customer.3cx
    .de -> customer-de.3cx.net
    Customer.3cx
    .us -> customer-us.3cx.net
  • Dual level domains
    customer.3cx
    .co.uk -> customer-uk.3cx.net
    customer.3cx
    .co.nz -> customer-nz.3cx.net
    customer.3cx
    .com.tr -> customer-tr.3cx.net
    customer.3cx
    .co.za -> customer-za.3cx.net
  • Exceptions domains
    customer.
    elastix.com -> customer-ecom.elastix.net
    City Domains are shortened to the first 3 letters
    customer.3cx.
    barcelona -> customer-bar.3cx.net

Note: 3CX reserves the right to revoke any FQDN which might

  • breach another company’s trademark rights
  • used otherwise than for the purpose of hosting 3CX
  • 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 (requires Standard, Pro or Enterprise Edition) 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. Every FQDN will also create a WebMeeting URL based on the following syntax:

  • userpart.hostpart.tld -> userpart-hostpart-tld.3cx.net
  • Samples
    customer.domain.com -> customer-domain-com.3cx.net
    customer.domain.co.uk -> customer-domain-co-uk.3cx.net
    pbx.customer.domain-part.co.nz -> pbx-customer-domain-part-co-nz.3cx.net

Altering the FQDN

Read here if you like to change an already bound FQDN: http://www.3cx.com/docs/key-already-bound/

Summary

  1. First time installation binds the FQDN to the key
  2. 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
  1. Subcentral installation of the same key required to enter the same FQDN
  2. 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

See also

You might also be interested in:

<