• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1164
  • Last Modified:

Reverse DNS issue

Finally figured out that our mail to AOL is being blocked due to incorrect reverse DNS config.  Spoke with our ISP yesterday and partially resolved the issue.

Our mail server - - now shows up correctly when using dns dig:
;; ANSWER SECTION:  3h57m6s IN PTR  mail.athomehealth.org.

However, our MS Exchange mail server is not named "mail", but "exchange".

Now, at DNSReport.com, I'm getting the error about "mail server host name in greeting",
mail.athomehealth.org claims to be non-existent host exchange.athomehealth.org:
220 exchange.athomehealth.org Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Tue, 27 Mar 2007 09:55:05 -0500

Now, we can't change the name of our server (because we have many internal laptop clients pointing to "exchange" as the mail server in Outlook), and yet I don't think it would be correct to have our ISP change the PTR to "exchange" instead of "mail", would it?

I'm sure there's a wise solution out there, but it escapes me at the moment.
3 Solutions
Try setting up a CNAME record in forward DNS to point mail. to exchange.
itatahhAuthor Commented:
But would that prevent our mail server from ID'ing itself as "exchange.athomehealth.org" instead of the correct "mail.athomehealth.org"?
itatahhAuthor Commented:
Increasing points - we've got outgoing mail to AOL piling up - need a solution.
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

The reverse DNS needs to resolve and match what the server announces itself as.

Therefore you either need to change what the server announces itself as, or get the ISP to change the reverse DNS. Personally I would change what the server announces itself as.

If email for AOL continues to pile up, use an SMTP Connector to push it through the ISPs server: http://www.amset.info/exchange/smtp-connector.asp

Don't forget AOL, along with many now, are getting quite picky.  the PTR record needs to match what your server announces itself as.  But the A record for its fqdn need to match the same IP that it connects with.
itatahhAuthor Commented:
Great solutions; thanks!

Our ISP indeed was mapping to the incorrect domain, and then I change our exchange server's FQDN to mail.athomehealth.org.   Also added a CNAME record.  
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now