On Sat, 19 Mar 2005, Tony Shiffer wrote: > He was trying to trouble shoot this from an exchange perspective which > wasn't so helpful - but the conclusion he came to was a DNS problem. He > writes that the DNS server in his MS SBS 2003 is intermittently faulty - and > that having his SMTP server use his ISP's DNS resolved the issue.
Exactly. They even tried to break the existing standards for DNS queries. > Then I thought about XMAIL and the choices we have. Without using > [SmartDNSHost] I think I remember reading that XMAIL just asks the operating > system to resolve DNS. Since none of our networks have any problems using > Microsoft DNS, I just didn't think it was the DNS server that was failing. > > So - I started using SmartDNSHost and pointing to the DNS server on the > machine on which XMAIL and the DNS server are running (instead of using > SmartDNSHost to tell XMAIL to use my ISP's DNS server as recommended in the > exchange article.) The Operating system itself, and the entire network it > supports are all configured to use the SAME DNS server, and does so without > problems. > > As soon as I began using SmartDNSHost, virtually ALL my lingering delivery > problems have ceased. Gone, poof! Zap! XMail, when used w/out the SmartDNSHost option set, perform full (from ".") DNS queries to get MX records. If you use SmartDNSHost, the query goes to the smart DNS host, with recursion bit set. Now, since all three reports came from MS setups, and since the MX resolution code is exactly the same for Unix and Win32, I lean towards the assumption that this might be some problem with the MS setup. A trace of the queries (and data received) done by XMail when used w/out SmartDNSHost would help. - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
