SMTP Reverse DNS Mismatch

Hello All,

I am currently running a Hybrid setup with Office 365 and my on premises Exchange server 2007.
Almost all of our Mailboxes have been migrated to the Office 365 but my MX is still pointing to my On Premises Exchange server 2007.

Today I went to MXtoolbox.com just to check on my status and found out that I have a SMTP Reverse DNS Mismatch which can cause some issues on incoming and outgoing emails to external companies.

The message says: "Warning - Reverse DNS does not match SMTP Banner"

Does this pertains to my PTR record?
LuiLui77Asked:
Who is Participating?

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

x
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.

Simon Butler (Sembee)ConsultantCommented:
I will give you a much shorter answer.

Ignore that "error".

I have outlined why in my blog here:

http://blog.sembee.co.uk/post/Exchange-2007-and-SMTP-Banner-Tests.aspx

Basically they are connecting to your incoming connector when the SMTP banner only applies to you outbound, which is on the Send Connector.

Simon.
0
JullezNetwork EngineerCommented:
Are you having issue with sending emails out?

In my case Comcast emails were bouncing back, not always, but 50% of the time, and creating the PTR record on ISP side resolved the issue.
0
JullezNetwork EngineerCommented:
Luilui77,

If you don't have any issues sending or receiving, you can ignore it, like Sembee said.

I had to deal with NDR's from Comcast because they didn't do their job properly.


So in case you get an error when sending like "route not found" here is what you can do:


Use this http://remote.12dt.com/ to check your PTR.

 Call your ISP, make sure they created a PTR for you, I had to deal with Comcast the last two days, because they didn't and I just couldn't get  to the right person to explain to them that they need to do it on their side....
0
LuiLui77Author Commented:
Thanks for your responses.

Sembee, great explanation on your blog. Will this be the case with Exchange 2013 as well?

I have another Exchange 2013 in house used for Line of Business applications (different FQDN and domain). This box is running in coexistence with my Exchange server 2007. When I perform a SMTP test I get the same Mismatch message.

If this is not the case, I guess that by changing my receive connector to the same FQDN of my send connector will do.

Tell me what you think.
0
Simon Butler (Sembee)ConsultantCommented:
The same problem occurs with all versions of Exchange 2007 and higher because of the dual connectors (Receive and Send).

If you have multiple Exchange servers then changing the FQDN on the receive connector can cause problems with email flowing between the servers. Microsoft don't actually support changing the FQDN to anything other than blank, NETBIOS or the server's real FQDN.

Simon.
0

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
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
Office 365

From novice to tech pro — start learning today.