|
We use SBS 2008 with Exchange 2007 for our inhouse email. Today I purchased BackupMX and reconfigured our MX records to have a second entry with priority 21 (1st entry is 11) pointing to the correct DynDNS backup mail server. Soon after, we started getting complaints from customers about email return failures. Also, my Exchange account on my Android phone stopped working because of certificate and authentication errors. I'm guessing that perhaps our Exchange Server might be taking too long to respond so mobile devices as well and customers sending emails end up having their requests go to DynDNS's server. I believe that this is the correct behavior except that these devices are falling back to the second MX record too quickly. Edit1 Any insight or suggestions on whether or not my assumption is correct as well as how to resolve this problem? |
|
As you didn't tell us your domain we can't check to see if your assumption is correct. How you resolve it depends on what the problem is - this sticky may help you work out what it is, and it lists the information we'd need to help you. It could be:
For Testing using MX Toolbox shows me that your server is responding, though not whether or not it'll accept email for the domain. If it isn't then that suggests a problem with Exchange's configuration. The domains are http://powerzone.com and http://powerzoneequipment.com. I've removed DynDNS's server/MX record for now to try to temporarily alleviate the problem. As per the list above, I don't think any of these could be the problem. As soon as I change the MX records back to how they were before, mail flows normally again.
Feb 07 at 07:57 PM
hk1
OK, I think I'm getting this problem figured out. And I don't think it has anything to do with DynDNS. It appears all of our DNS entries got cleared and reset this morning by our web hosting company. That's what has everything screwed up. After I confirm that I'll post back here.
Feb 07 at 08:11 PM
hk1
|
