Control which public IP exchange 2k3 uses to deliver mail?
Posted on 2007-09-27
I have recently been reports from users that email messages are getting bounced back to us from some of our clients. The most recent error says: "Your IP xxx.xxx.xxx.130 does not have a reverse DNS entry"
The way our network is set up currently is basically like this: T1 > Cisco > Watchguard Firebox (doing the NAT) > and our handful of public IPs are assigned on its interface: .130 - .136. A few months ago, we moved our mail server (and accompanying DNS & reverse DNS) from .130 to .132 because we set up a dedicated exchange 2k3 server. But, apparently, when our server connects to another to deliver mail, the .130 address is showing up, which doesn't match our DNS or rDNS.
Any ideas on how I can fix this? The MX, in case anyone wants to do some checking, is mail.wrightengineers.com