11-18-2010 09:31 PM - edited 03-11-2019 12:11 PM
I imagine this solution is out there but after browsing posts for an hour I can't come up with it.
Below is my network and were using an ASA 5550 8.2.3.
outside 12.12.12.0/24
dmz 10.10.12.0/24
inside 10.10.0.0/24
static (dmz,outside) 12.12.12.10 10.10.12.10
What I need to be able to do is from the inside access a server on the DMZ via both the 10.10.12.10 address as well as the 12.12.12.10 IP. I can get either or to work but cannot get them both to function at the same time. Ideally it would be even better if when you connected to the 10.10.12.10 ip address it returned the 12.12.12.10, but that's not a 100% necessary.
This scenerio works like a champ on the PIX and 6.3.5 code via the static (dmz,inside) 12.12.12.10 10.10.12.10 dns command.
Any help would greatly be appreciated.
-John
11-19-2010 12:36 AM
Hi John,
Is your DNS server external ?
Please confirm.
Cheers,
Nash.
11-19-2010 07:07 AM
I wish we had a single DNS. Unfortunately I inherted quite a mess.
We have internal and external DNS both serving our FQDN (*.acme.com). For the life of me I cannot come up with one good reason why someone would do this but it's here and it's not going away.
I though I came up with a work around but the 3750's that act as the L3 on the inside do not support NAT so now I'm really in a bind.
-John
11-19-2010 08:55 PM
Hi John,
I am not sure if you got an answer to this one. But in 8.2.x and earlier releases of ASA its not possible. But in 8.3.x and later releases it is possible or at least i have seen it work. Please refer the below link for more information on that:
http://www.cisco.com/en/US/docs/security/asa/asa83/configuration/guide/nat_overview.html#wp1107407
let me know if this helps!!
Cheers,
Prapanch
11-20-2010 09:26 AM
static (dmz,outside) 12.12.12.10 10.10.12.10
What I need to be able to do is from the inside access a server on the DMZ via both the 10.10.12.10 address as well as the 12.12.12.10 IP.
Like Prapanch says that is not possible and will give you an error when you try to configure in the form of two statics
and if you do nat 0 with acl and destination static combination then you will end up with nat RPF check failing message.
The best thing to do is to fix the dns servers and make sure they only hand out the internal 10.10.12.10 address for the inside users.
As far as using external dns and it resolving to 12.12.12.10 make sure to add the "dns" keywork to the static
static (dmz,outside) 12.12.12.10 10.10.12.10 dns
DNS inspection should be enabled so, when the dns response comes back as 12.12.12.10 it will be changed to 10.10.12.10.
-KS
11-20-2010 11:38 PM
Thanks for the replies.
Actual it will work in 8.2 but it's much easier in 8.3.
Here is what I did in 8.2.
Create and acl for the servers dmz ip and the internal network - access-list dmz_nat extended permit ip host 10.10.12.10 10.10.0.0 255.255.0.0
Now you tie the two ip addresses (real and public) to the static
static (dmz,inside) 10.10.12.10 access-list dmz_nat
static (dmz,inside) 12.12.12.10 access-list dmz_nat
I was able to connect to either IP address from the internal networks to the dmz without issue. It's a little messy but atleast it's a solution as eliminating a internal name server from a billion dollar a year company isn't. I didn't create the mess I just inherated it
-John
11-21-2010 03:53 AM
Hi John,
Glad to know you managed to get it working and thanks for posting the configuration as well.
Regards,
Prapanch
11-21-2010 05:35 AM
Oh my ! I forgot about this trick again. My bad !
http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807d2874.shtml
-KS
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide