Reverse DNS issues but related to Cisco ASA Firewall
So I have recently upgraded my Exchange server from 2003 to 2010 and mail seems to be flowing perfectly however the reverse DNS doesn't work
In my firewall (cisco asa) I have the following NAT configuration for Inside network:
Static - Source (192.168.1.8) - Interface (Outside - 178.10.123.123) - Address (Webmail = 178.10.123.30)
With this NAT rule I can run ActiveSync, Webmail, etc.. all from outside of the network however my Reverse DNS doesn't work but if I change it too:
Static - Source (192.168.1.8) - Interface (Outside - 178.10.123.123) - Address (reverse dns = 178.10.123.254)
Everything works like a charm for Reverse DNS but now my Webmail and ActiveSync no longer work from outside.
If I try to create 2 of those NATS one for webmail and one for reverse it tells me that "an overlapping error occurred and cannot be completed"
Before on my old server I had OWA and Exchange on two separate boxes, but now that there all on one box I cannot figure this out.
Thank you for all your help
In my firewall (cisco asa) I have the following NAT configuration for Inside network:
Static - Source (192.168.1.8) - Interface (Outside - 178.10.123.123) - Address (Webmail = 178.10.123.30)
With this NAT rule I can run ActiveSync, Webmail, etc.. all from outside of the network however my Reverse DNS doesn't work but if I change it too:
Static - Source (192.168.1.8) - Interface (Outside - 178.10.123.123) - Address (reverse dns = 178.10.123.254)
Everything works like a charm for Reverse DNS but now my Webmail and ActiveSync no longer work from outside.
If I try to create 2 of those NATS one for webmail and one for reverse it tells me that "an overlapping error occurred and cannot be completed"
Before on my old server I had OWA and Exchange on two separate boxes, but now that there all on one box I cannot figure this out.
Thank you for all your help
It would be helpful to get a scrubbed config. Also, inbound nat rules don't necessarily mean that the outbound traffic will use the same IP address. I would hop on the server and go to a site like www.ipchicken.com or something that shows your external IP address and you may find that outbound traffic uses a different public IP than the inbound traffic.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I fixed this myself, this is the correct way in making it so you can receive mail to your Barracuda spam and virus firewall and be able to send out on another public IP with Reverse DNS working perfectly
Try to do reverse DNS and be at the same time connected to ASA box... Submit logg here, so we can see where is the catch...