You could do that with 1:1 NAT instead of having public IPs directly on the
servers.
Then you simply need to update DNS records pointing to the other IP. You
could have multiple failure layers there - default gateway redundancy
through your ISP, external services monitoring the IP,s and triggering DNS
update in the event of a certain failure.
On Wed, Nov 6, 2013 at 11:41 AM, Matthew Poole
Well, it's a right nuisance trying to deal with things if the addresses need to change, but having two very-much-competitor ISPs providing different addresses over two different physical links would seem to make that a necessity. So it's then about how to handle triggering the change in DNS records and routing for multiple servers that have public IP addresses in as seamless a manner as possible with the shortest possible delay between link 1 failing and link 2 becoming the path for inbound and outbound traffic.
On 6/11/2013 11:35, Chris Jones wrote:
How important is it that the addresses stay the same?
-- Matthew Poole "The difference between theory and practice is that practice is easier in theory than theory is in practice"
NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
-- Regards, Mark L. Tees