Re: Multihoming an end user
At 10:30 PM 9/23/05 -0500, Rich Puhek wrote:
>This wouldn't help with your Watchguard, though. If your primary link
>went down, clients would have to change how they connected. One
>possibility would be if you controlled your own DNS (and if the clients
>connected by name instead of IP), you could have the same script that
>monitors your Internet connection take care of changing the DNS entry to
>point to a secondary IP on the Watchguard (from the secondary ISP's IP
>block).
Changing the DNS entries on the fly isn't a workable solution because the
change won't take affect until all the remote caches expire. If u need
general inbound redundant connectivity multihoming is the only solution. If
u only need outbound connectivity then u could get away with just swapping
the NAT. U can keep the VPN working with this setup by giving the VPN
server IPs on both links and putting both IPs into the VPN client. Clients
would then just pick one.
--
REMEMBER THE WORLD TRADE CENTER ---=< WTC 911 >=--
"...ne cede malis"
00000100
Reply to: