Can Cisco resolve internet address internally

Here is the situation.  I have an internet domain of CORPORATION.COM

Exchange is the mail server with the DNS name of MAIL.CORPORATION.COM on the internet.

MAIL.CORPORATION.COM is used by laptop, (for example), for Outlook Anywhere access.

MAIL.CORPORATION.COM resolves to internet address of 200.250.192.100  (again, just an example)

My Cisco ASA NAT's the external IP of 200.250.192.100 to the internal LAN address of 192.168.1.50

All of that works great.  No problems.

However, when someone with a laptop comes into the corporate office, and tries to resolve the name of MAIL.CORPORATION.COM,  the internet DNS responds with 200.250.192.100 which the Cisco is unable to resolve or map back to the internal network of 192.168.1.50, which is the Cisco's internal known IP network.

For years, the way around this is to set up on the INTERNAL LAN DNS a CORPORATION.COM domain, that all local LAN clients would use to resolve back to the internal LAN network of 192.168.1.y, instead of to an external Internet address.

Frankly, I HATE that solution.  I always thought it was kludgy at best.

So, the question is this, is there a way to configure the Cisco that if it sees an internet address that maps to its known internal LAN network IP, it will automatically respond back with that internal LAN address instead of just getting stuck in a loop?

Thank you in advance,
Jeff
jgrammer42Asked:
Who is Participating?
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.

footechCommented:
In my opinion, a split DNS really is the best way to handle things like this (not sure why you would consider it kludgy).  If you only have one or a few resources that should resolve to a different IP depending on whether the client is on the internal network or coming over the internet, then you can create specific zones for those resources rather than creating one zone to cover all of CORPORATION.COM.  For example, you would create a zone for MAIL.CORPORATION.COM and then create an A record in it with a blank name which points to the internal IP.  This leaves other queries for records in the CORPORATION.COM domain (anything not like xxx.MAIL.CORPORATION.COM) free to be resolved by records on the public DNS.

I've no clue whether your Cisco could do what you ask, but I would be quite surprised if it could.
0
Craig BeckCommented:
You can do DNS rewrite (commonly called doctoring) at the ASA...

https://supportforums.cisco.com/document/145401/dns-doctoring-and-u-turning-asa-when-and-how-use-it
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
jgrammer42Author Commented:
Hi Craig,
This appears to be exactly what I was looking for.  I will test this out this weekend and see how it works.

Thank you,
Jeff
0
jgrammer42Author Commented:
thank you
0
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
Routers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.