I have a installed in exchange server 2013 in the Home network. Everything looks fine. But Reserve DNS was not setup properly.  Reverse DNS is not matching with my domain. "Reverse DNS does not contain the hostname" when I checked in MXToolBox.com 

I have configured FQDN on port 25 to mail.xxxxx.com. I don't know what else need to configure as Iam new to exchange. 

Can some give me some steps to do this?

Do you have a purchased DNS domain that you use to test this in a home network ? If so, you should have access to the reverse (PTR) records and be able to modify them so that they reflect your environment.

I also suggest going the following thread for more information: https://social.technet.microsoft.com/Forums/exchange/en-US/fdbc68de-8ad9-4eae-963b-5ded5c5849ca/reverse-dns-does-not-match-smtp-banner.

Hi,

Reverse DNS does not match SMTP banner appears if you did not configure your SMTP Banner properly.

It tries to resolve your reverse DNS and then it compares the result to the SMTP banner you configured

Please see https://technet.microsoft.com/en-us/library/bb124740(v=exchg.150).aspx how to adjust your smtp banner.

Let me know, if it resolved your issue.

Regards,
Martin

Reverse DNS (aka PTR record) is something set at your ISP level, not on your Exchange server. If you have a static IP from your provider you should be able to contact them (or log into the ISP's portal) to change the reverse DNS. If you have a dynamic IP (meaning you didn't pay extra for a static) you will be unable to set your reverse DNS.

The implication's of not having a matching reverse DNS is that many email providers will not allow you to send them email (ex. aol.com, hotmail.com). I am actually in the same boat (on a dynamic IP) but I set up my Exchange to send all my email through a spam filter service. If you send through a reputable spam filter you should have no issues sending to any email providers (even though reverse DNS checks will still fail). 

• Proposed as answer by Alceryes 12 hours 56 minutes ago
• Edited by Alceryes 12 hours 56 minutes ago