So I have been kicking this thing around my head (and google) for some time now.
My scenario: Two data centers connected via MPLS, each with their own internet. We have replication setup for our VMs to the "Passive" datacenter. Each data center has its own address space. I want to setup NAT at our main datacenter such that when the VMs failover the internal IP is changed to the new IP at the "Passive" datacenter and traffic is sent over MPLS. Right now we have to wait for DNS propagation which is not ideal. I considered going the BGP route but have different ISP's and one isn't being cooperative.
This is our current architecture.
Active ---------mpls-------- Passive
1. Anyway to use internal DNS for the Inside nat address?
Unfortunately I have no additional funds in the budget to accommodate this. Below is the current build with equipment involved. If I could use a DNS name in the NAT statement that would solve all my issues. But as far as I know thats not possible.
As you can see below LISP is not an option. Just need ASA's to send the traffic to the New IP when the VM's move. The old IP will be offline (non-pingable) when the failover happens. Which makes me think maybe IPSLA?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...