Re: Reverse DNS

  • From: Danny <nocmonkey@xxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 31 Aug 2004 15:40:39 -0400

On Tue, 31 Aug 2004 14:14:10 -0500, Clay Niemann <clayn@xxxxxxx> wrote:
> Hi. My company recently implemented an Exchange 2003 server. Most messages
> are sent and received fine. However, some messages to larger providers like
> AOL and Yahoo get delayed for a couple of days then fail altogether. I have
> verified that I am not on a SPAM blacklist.
> After looking around on Google I suspect the issue is related to reverse
> DNS. The domain name that supports our LAN is fake (it isn't registered). We
> do have a separate domain name for email that is registered. DNS hosted by
> our ISP points the real domain to our Exchange server. They also configured
> reverse DNS. We have an internal DNS server for hosts within our LAN.

I suggest using your ISP's mailserver as a SmartHost, so that outbound
email is relayed through your ISP's properly configured (RDNS, etc.)
SMTP server.

Run a test during non-peak hours, and configure your SMTP settings (In
Exchange System Manager)  -> SmartHost -> your ISP's smtp server. And
send a few test messages.

Yes, we could go more into depth about your DNS configuration, but I
like to keep things simple. Either way, I am sure that we can help
improve your mail delivery issues.


Other related posts: