Reverse DNS

Posted on 2011-02-24
Last Modified: 2012-05-11
We have 3 main sites each with there own Exchange 2010 server, MX records are pointing to one site which collects mail for multiple domains (different sub companies) and then distributes them to the corresponding mailboxes, this was found to be the best setup as users from the sub companies are spread across different sites..
Each site though sends out using it's own exchange server, the problem we are getting is with reverse DNS which resolves to the one site so we are getting bounce backs from certain mailservers as the rDNS does not correspond with the sending site.
The way I see it is that I can't have one A record pointing to different ip's as when I enter this as an MX record mail will be sent to both, great for load balancing but not for our set up were we only want one server to receive external mail. how would I go about setting up multiple ip's for a single MX record?
Question by:carn
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
LVL 15

Expert Comment

ID: 34969168

Accepted Solution

Saineolai earned 125 total points
ID: 34969191
The reverse dns lookup should be for the fully qualified domain name of the sending Exchange server's smtp service.

Ensure that reverse lookup for each IP address matches the fully qualified domain name on each server.

Author Comment

ID: 34969323
Thanks saineolai don't know why I was thinking it had to match the MX? when you say FQDN are we talking internal or external ie. when I telnet to our mail server on port 25 it responds with it's internal domain name.
PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now


Expert Comment

ID: 34969345
It should be dns name that it responds with when you telnet to it from the outside of your network.

This should be an external domain name, although if not configured in the Exchange configuration it will use the internal one.

Expert Comment

ID: 34969354
Have a look under FQDN on this page:


Author Comment

ID: 34969362
would there be any problems with using the internal (which is what it responds with externally)

Expert Comment

ID: 34969422
You ISP will not create a reverse dns entry for a private dns zone (.i.e., company.local).  If the internal dns zone is a valid domain e.g. .net, .com .org then there should be no problem.

Featured Post

Forrester Webinar: xMatters Delivers 261% ROI

Guest speaker Dean Davison, Forrester Principal Consultant, explains how a Fortune 500 communication company using xMatters found these results: Achieved a 261% ROI, Experienced $753,280 in net present value benefits over 3 years and Reduced MTTR by 91% for tier 1 incidents.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

#Citrix #Citrix Netscaler #HTTP Compression #Load Balance
Don’t let your business fall victim to the coming apocalypse – use our Survival Guide for the Fax Apocalypse to identify the risks and signs of zombie fax activities at your business.
After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor ( If you're looking for how to monitor bandwidth using netflow or packet s…

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question