Should i be provisioning with the fqdn or the local ip server for new app?Should work anywhere. Though, I think if you have connected to 3CX using a LAN IP and not its FQDN, it creates the URL/QR using the LAN IP? Log in using the FQDN.
This is what I got in host AThe A for your fake/split DNS zone should be the server's LAN IP.
When you (or the user generating the QR) connect to your 3CX server in your browser, do you use the FQDN?
Basically, don't connect using http://10.10.x.x.

You should create a dedicated zone for your full FQDN and use the "root" record of that zone.This is what I got in host A
View attachment 43429
I started to riff on this but I think 3CX has changed the doc page to use the FQDN as the "zone name" which I've posted before is much better, so I agree.You should create a dedicated zone for your full FQDN and use the "root" record of that zone.
Otherwise it becomes "myname.in.3cx.us.yourdomain.local"
No, make a new forward lookup zone.So I shouldnt have made another zone on its own for my records it should have been under my root zone of my domain if I am understanding correctly.
Which I did do. Host A is the internal IP address along with my FQDN copied from 3cx.No, make a new forward lookup zone.
Founded in 2005, when VoIP was an emerging technology, 3CX has gone on to establish itself as a global leader in business communications.