Changing FQDN, what other consideration to plan for?

[ArtR]

Hi All,
Reading about changing our FQDN as the existing one shows our company name, and as we want to run some sub-brands its not ideal so looking to make it more generic.

Found another post where YiannisH says to do:-

Please note that in order to change FQDN you will need to re-install the system. To do so:

• Create a backup of the system without licence and FQDN information
• Un-install the PBX
• Access the costumer portal and release the key from the current FQDN
• Re-install the system using the licence key and your own FQDN.

Please note that you will need to also provide a certificate for your FQDN and that custom FQDNs can only be used with a PRO or Enterprise edition key.

But what else do we need to take into account?
Do we need to resend all the users their account info emails again so their config/qr code points them to the new FQDN, or will the system do that automatically when doing a restore?
Anything else to be aware of?

We don't have many users but we do have a mix across a few locations so i'm trying to cover off all aspects to get this done during our quiet xmas period.


Thanks all.

a.

 

[cobaltit]

Short answer is yes. But if you really want to cover your bases and feel comfortable with the process I'd recommend getting a free key and doing a test run.

 

[JohnS_3CX]

Hi ArtR,

Like @cobaltit said above, the answer is yes. Practically anything that contains the FQDN will need to be reprovisioned after the change:

• STUN Devices
• SBCs
• Devices connected to SBCs
• Mobile Clients
• Desktop Clients
• Webclient users (they just need to know the new FQDN to log in to)
• Bridges (if you use any)
• New WebMeeting, Click2Call, Click2Meet URLs may need to be updated
• Any integrations you may have that relied on FQDN (ie WordPress)

As for the sub-brands you mentioned, if you plan to use your own FQDN, you can not have wildcard certs that go beyond one level of subdomain behind the wildcard:


Example: Wildcard Cert = *.group.com
company.group.com - OK
department.company.group.com - Not OK


Example: Wildcard Cert = *.my.group.com
company.my.group.com - OK
department.company.my.group.com - Not OK