Local hosted Server serves with FQDN locally

[Ashelis]

Hello,
After installing 3CX into our locally hosted server, other applications and servers started to know that server with 3CX FQDN
I couldn't fire it out. I'd be glad if someone can assist me.

How can I revert this?



(I blurred some parts of screenshots but I don't know which parts are crucial)
Example:
Real Server Name: SRV.domain.local
Local Server IP: 192.168.100.YYY
Announced Server Name: CompanyName.3cx.com

 

[nobody]

The 3cx pbx most likely has registered its name on the DNS Server, If you want to undo this, check the A entries in the DNS servers database. Using a split dns where inside the network the fqdn of the external name points to the internal ip resolves most of the problems with certificates, so I would recommend to keep it like that.
Still you have to live with the certificate errors, because you never will get a certificate for a ".local" domain, or a "192.168.x.y" domain with the exception if you run your own private certification authority. But even if you generate your own certificates I recommend to use the the split dns.

 

[Saqqara]

As above setup split dns - https://www.3cx.com/docs/creating-fqdn-split-dns/ so that devices on your internal network point to the internal 3CX ip address