Split DNS

[Lakes]

Hi, we use split DNS so that clients on the LAN connect straight to the on-premise 3cx server, when off the LAN, they can connect through NAT.
I'm finding the web client (and the windows client) don't reconnect if the client experiences a network change - wired to wireless or, if working remotely, a brief drop in wireless or starting the VPN connection.
This isn't about calls dropping, it manifests as being unable to answer an incoming call when it rings, or can't dial out (internally or externally)
The only fix seems to be to restart the client completely.
As a test, I've paused the internal DNS and things look more robust, is it just me experiencing this issue?
Thanks

 

[JohnS_3CX]

Hi,

This is an inherent network restriction effect, allow me to explain in some detail:

1) the browser uses a connection path to connect to a server ie. gmail.com to read your emails

2) Suddenly there is network change, meaning that the old path is now invalid and the current flow of data is disrupted

3) Chrome is not yet aware of this unless something happens ie. you need to click on something that wants to fetch data such as opening an email

4) Chrome will try to fetch it, realize that the path is no longer valid and re-initialize the connection to the site over the new network path it just discovered. This will won't happen as soon as you've switched networks unless you trigger it by refreshing/reloading/relaunching Chrome. Different elements of the page may connect independently (ie. the chat window is still not working even though you did load that email eventually) so you can't avoid refreshing.

Since the webclient relies on Chrome and in turn a stable connection, you will face this issue with pretty much anything that loads via Chrome. It's neither the fault of the browser nor the site, the issue is that you cut the link and connected elsewhere causing a network disruption.

It's best practice to launch the VPN before you launch any apps, or at least re-leaunch all of them after a network change.

Hope this helps!

PS: Pausing the internal DNS should not really make much of a difference. If a network change occurs, new paths need to be re-established regardless. It's a bit more complex than that, but that's a whole new chapter

 

[Lakes]

Thanks for the reply, it's good to have an explanation. I have been advising staff to start apps last and the pre-logon option on our VPN should help there.
I put split-DNS back in place pretty quickly as it stopped me accessing the console which is restricted to onsite only.
Useful information, thanks again