Sorry for the long note. Any help would be appreciated.I have a Domino 8.0.2 server running on Win2003 server. There are times when the server will stop communicating with other email servers. The problem has to do with the inability of the Domino server to resolve the MX record of the other email server. Not sure why this happnens in the first place, but I was told several things like slow bandwidth could cause this to happen. Anyways, when the Domino server fails to get the MX record, the server will revert to the domain’s “A” record in DNS for trying to deliver mail. This of course is not typically going to be the MX record for the particular domain. At that time the Domino box keeps the “A” record in the cache and will keep trying to send email to the “A” record. This of course bounces user’s emails and causes me to have to stop and start the router to fix (clear the cache) issue.
This problem has been going since version 5 of Domino. It was apparent on the Win2k server and Win2003 server boxes that Domino had run on and is currently running on.
I have called Tech support and they tell me to add some lines in the notes.ini to hard code the dns servers addresses within Domino, but that does not help solve the root cause of the problem. The also mentioned this issue is with windows and the way DNS requests are being handled. I had an SPR created for this problem, but no resolution other than to have a program scheduled to restart the router.
This is getting very frustrating for me.
Ever since version 5. I am losing faith in Domino development and their inability to fix a major problem like this.
I am having the same problem. As I understand reverting to using the A record in the event an MX record is not found is in keeping with RFC 2821 section 5. I don’t particularly understand why, but there you have it.
The real problem comes when Domino never flushes it’s cache. It wouldn’t be so bad if Domino would at some point try the lookup again. In the cases where I have had this happen it’s usually because the domain in question actually did have some DNS errors but fixed them soon after, or the Domino server received an incomplete reply from the DNS server and so used the A record in the absence of an MX record. But upon checking my DNS server only a few hours later the MX records were indeed there. So if Domino would just check again the problem would resolve on it’s own.
As a temporary work around I used the approach that Mael Rivera suggested in his response to this post.
On a more permanent basis Passport Advantage has linked my PMR 41706,442,000 on this to SPR JFBM7C6GA4 which is in turn linked to APAR L033942 (Enhancement Request).
I would suggest that you have your PMR linked as well as the more problems that are linked will add more weight to the enhancement request.