Solved Custom FQDN - Is there any reason to use one?

[greychain]

Is there any technical/security reason to use a custom FQDN?

 

[Saqqara]

If you use 3cx fqdn - all fqdn dns updates and lets encrypt ssl renewals are taken care of thru 3

Custom fqdn - you managed your own dns and updates of the ssl certificates - extra work for you

No technically reason to use your own fqdn - unless your company wants the web url (mangement, client web), and remote devices to have your own fqdn

No difference in security

You can only use your own fqdn on pro or enterprise license

 

[Alphabetic]

Some bigger MSP's will use custom FQDN for their own white labelling.. but I see posts on here all the time with stuff breaking because they use custom. Save yourself the headache and admin and stay with 3CX's.

 

[greychain]

Haha that was part of the 'Let's see how much trouble having your own FQDN project is'.

Even worse using LE behind a SNI-Proxy

 

[VasilisV_3CX]

I think this has been adequately answered by our partners. I'll close this and if you have any further questions on the topic, feel free to PM me or open a new thread!