Issues with Exchange 2013 reverse DNS, FQDN, and bouncebacks.

I'm getting an increasing number of messages with  "Reverse DNS for x.x.x.x failed."  We don't have a Reverse DNS record setup, and I need to.  When I check the headers sent from my organization to a test gmail account I've set up, the FQDN is the internal FQND of the machine's host name on my local LAN, not an FQDN associated with the internet domain name of our organization.  Upon review this seems incorrect, but would like to solve this.  What should the FDQN in the header actually be?   Where do I change this in Exchange 2013, and what impact will that have on mail flow as soon as I do change it?  I would imagine once this issue is corrected, I can create the proper PTR/Reverse DNS record and all will be well.  Any info would be helpful, thanks!
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
For Exchange specifically to work you are required to have a MX record and your Reverse External IP pointing to the IP of your MX record. This is a minimum requirement for sending email on the internet withou being flagged as spam. Another thing I would suggest is creating an SPF record as well.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LB1234Author Commented:
Will, we have the uncommon situation of our MX record being hosted by a third party, which is not the same server/domain we send mail from.
Will SzymkowskiSenior Solution ArchitectCommented:
If you are sending mail from a different mail server then where mail is received from you need to add that Sending Servers external IP address to the SPF record. This way when the email is sent it states that this external IP is a legitimate IP addresss for sending mail on behalf of this domain.

If you do not do this, this is where you run into issues of being blacklisted as you look suspicious to Anti-spam appliances.

Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
Nice answers Will :)
LB1234Author Commented:
Thanks!  I called my ISP and told them to setup my PTR record and they went right ahead and did it.  For those who may be reading this, do not go to your domain host and ask for this, but rather the vendor who provided your block of IP addresses.
Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
excuse me for saying that but you should be giving him 500 points here, he spends a lot of time helping the community and is the best expert on here, imagine if he wasnt here to help you!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.