Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 477
  • Last Modified:

Reverse DNS

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?
0
carn
Asked:
carn
  • 4
  • 2
1 Solution
 
JBond2010Commented:
0
 
SaineolaiCommented:
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.
0
 
carnAuthor Commented:
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.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
SaineolaiCommented:
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.
0
 
SaineolaiCommented:
Have a look under FQDN on this page: http://technet.microsoft.com/en-us/library/aa998662.aspx

0
 
carnAuthor Commented:
would there be any problems with using the internal (which is what it responds with externally)
0
 
SaineolaiCommented:
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.
0

Featured Post

Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

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