Madas said:Most routers tell the clients (through DHCP) to use the firewall for dns resolution. Then you firewall will make the DNS requests to the outside world. If something has recently been queried then your firewall will cache the DNS resolution and will NOT go out the internet. This will still return a valid IP to the requesting device for some period of time even when your internet is down. My IPDataTel seems to failover much quicker when the DNS resolution fails vs when the DNS resolution succeeds but the connection itself fails.
It definitely made a difference in my setup.
I don't know how to find the firmware version. I have a HAI panel so its not hooked to my keypads as it would be in a DSC
Ahh. I see. Well I've been through 3 different routers since I this has been an issue. A d-link dir-655. Replaced 2 weeks ago with a TP-Linc AC5400 which was crap and had to be sent back because it kept dropping wifi and ethernet(not at the same time) and the UI would on the device would freeze for 30 seconds at a time every 10 seconds making it difficult to configure. Replaced that last week with an Asus AC1900 which has been great. No issues.
All three routers were using the stock DNS settings and CBAT has behaved the same through all three. On Friday we disconnected the CBAT from IP and alarm relay is monitoring both my EVL4 through IP and the CBAT through Verizon, so I'm good for now.