Support => Email FAQ

Dec 2015 Email Server Transtion


Teztech has recently upgraded its email servers. Most customers will not need to make any changes to their email configuration. No customers should need to change passwords. Please see the troubleshooting information below. This article's primary purpose is to provide access instructions to the old mail filtering servers and troubleshooting instructions.

Email Filtering Access

Our mail filtering servers have been completely replaced with new servers. The new servers do a much better job of filtering spam, viruses and other unwanted email. We have imported all your accounts and settings into the new mail mail filtering servers. However, we did not import your old, quarantined emails into the new servers. For a limited time, we are providing access to the old mail filtering servers at the following url:


Although every effort has been made to update hostnames (for example, with the IP addresses of our new email servers, some users will have difficulties due to DNS caching provided by their ISP (for example, Comcast, TimeWarner or Verizon) or their computer, tablet or smartphone. Many email clients will report the problem of old DNS information with an appropriate error message such as Failed to connect to server. However, a few significant email clients such as Outlook often report any type of connectivity problems by erroneously prompting for a new password. You do not need to change your password! Please see the troubleshooting instructions below.

The first troubleshooting step is to simply reboot your device. Many devices automatically flush cached DNS information when they are restarted. If that doesn't work or you would like to try to flush your DNS cache without rebooting your device, locate DNS cache flushing instructions for your device. Here are some example searches:

If you've rebooted and cleared your DNS cache, then the problem is likely on your ISP's DNS server. Theoretically, this should never be a problem. Our DNS servers tell other DNS servers to reload our DNS information every 5 minutes. So, at least in theory, assuming you aren't having a client DNS cache problem, the most you should have to wait is 5 minutes. In practice, we've noticed that many ISP's DNS servers cache DNS information longer than they should. In this case, you have these choices:

  • Wait and hope that the problem eventually resolves itself. If you decide to wait it out, be sure to reboot periodically to flush your client DNS cache.
  • Call your ISP's support department and convince them to flush their DNS cache for the related domains (for example,, and
  • Use different DNS servers that have up-to-date information

We've had good luck using Google's DNS service when our cranky ISP DNS server isn't working well. Here are some searches for instructions to get you started:


We know change is hard, but the new servers are faster, more reliable, filter mail better and have new features that we'll be telling you about soon. We think we think you will soon come to appreciate the change and we thank you for your support!


If your question isn't answered here, ask our support team directly,
or call 678-268-4065 and choose option 2 for support.