That was the first thing I did (dns), I have internal and external dns (2 inside (ddns) and 1 outside, that are my boxes), all of them have records for the mail server, but even with having all of this wonderful dns in place outhouse still barfs sporadically, now I was using outhouse express instead of outhouse and I could put in pop.cuinc.org or smtp.cuinc.org and presto it would work great, but not with outhouse (since all we are using is outhouse I pulled those records), I finally just gave up on the sporatic problems by using the ip addy of the server it's self, outhouse still gets sporadic issues but not near as often, it might appear to be a short sighted opt. at first but trust me with the calls I was getting, anything to cut them back was a good thing (mind you I had to go to every machine and change these settings manually from pop.cuinc.org to the ip).
Bob T. Kat "When everyone's out to get you, paranoia's just good thinking!" -- WKRP's Dr. Johnny Fever Kenneth wrote: Seems like a short-sighted optimization. Instead, run a local DNS server that you control, so your resolution issues are your own. Create a local DNS record (eg. mail.mycompany.com) that points at the right mail server for your clients. (I create separate records for each service, eg. smtp.mycompany.com, pop3.mycompany.com, etc.) Then your clients will resolve against a known good name server, and your configuration is in one place, where it's easy to change if need be.
