DNS Resolution on TEAS Server needs to be fixed

[Jonmccombs]

The TEAS server looks to the Cisco Meraki for all DNS URL resolutions. This was experienced on all units and was fixed by changing the TEAS units from a static IP address to Dynamic IP address and having the Cisco Meraki hand out the same IP address to the unit effectivity making it a static IP address. I tried to do the same with the server but the TEAS software will error when changing from Static to DHCP. Email and SMS can not be sent from server until this issue is resolved.

[Jonmccombs]

I will work with AirQual on the best resolution to this issue. It is a minor fix. I will alter the network interface settings to use Google DNS server and should resolve this issue . This will require the server to be restarted so I would like to wait until dialog is done with AirQual and someone such as Joshua is on site to reboot the server if it inadvertently hangs during setting change.