The MX lookup used UDP which is not as reliable as TCP (most lookups are UDP, however
- except for zone transfers). At any rate,
make sure that you have MX caching turned on - as a matter of fact, I kind of wish
that we didn't even make that an option and that
MX caching was always on no matter what...
HTH,
Howie
----- Original Message -----
From: "Mark Idzik" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Thursday, February 07, 2002 1:17 PM
Subject: [iMS] MX resolve problems
> Hi All,
>
> I'm using IMS Post SE (just recently upgraded to the 2.1.8
> exe file) and ran into a problem yesterday.
>
> The log files are starting to show that the system can not
> resolve the MX record for any domain.
>
> WARNING: Error resolving MX from server 208.233.88.10 for
> yahoo.com
> WARNING: Error resolving MX from server 208.233.88.10 for
> aol.com
> WARNING: Error resolving MX from server 208.233.88.10 for
> hotmail.com
>
> I have 5 dns servers listed and all are up and running ok.
>
> There were no changes made to the server, and the network
> connectivity is OK because all other functions run fine. I am using
> MX caching and resolve from address options.
>
> Any ideas why this is happening? Everything has been running
> smoothly for the past month since the upgrade.
>
> Thanks!
>
> Mark
>
==^=======================================================
This list server is Powered by iMS
"The Swiss Army Knife of Mail Servers"
--------------------------------------
To leave this list please complete the form at
http://www.coolfusion.com/iMSSupport.cfm
Need an iMS Developer license? Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [email protected]
==^=======================================================
