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

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

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

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

Hi John,

Glad to know you managed to get it working and thanks for posting the configuration as well.

Regards,

Prapanch

Oh my ! I forgot about this trick again. My bad !

http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807d2874.shtml

-KS