I have found out that BGP is configured to advertise the HQ subnet of
184.108.40.206 out of the DR site during a failover of the HQ Internet connectivity, or an entire site failover.
Since this is the case, I do not need the DNS solution, but I will still need to put the second CSS in the DR site.
This brings up this problem:
I have the one CSS configured in the HQ site with services and VIP's in
the 220.127.116.11 subnet and is is working.
If the primary server is down, the CSS points to the DR server NAT configured
in the HQ PIX, and the traffic is routed tthrough the HQ PIX through our
internal MPLS cloud to the DR server.
The DR site has it's Internet in the 18.104.22.168 subnet.
The DR pix had it's outside Interface configured in the 22.214.171.124
subnet, but has static NATs for the servers in HQ AND DR the same as HQ, in the 126.96.36.199 subnet.
This way, when a failover happens, DNS does not need to be changed.
So what this means is I will have to configure the CSS services and VIPs pretty much the same as the CSS in the HQ site.
What I am not sure about are these three things:
1. What IP Address subnet do I put the CSS interface and server services in? I will put the VIPs
in the HQ subnet 188.8.131.52, due to the fact that BGP will route to this subnet, but how do I set up the CSS interface itself?
2. Do I need to set up communication between the HQ CSS and the DR CSS through an App service?
What would I gain in my scenario? I am not sure it will help me much in this
3. Can I set up the DR site services with the same addresses as the HQ site services?