I don't think I understand the question. In a hub & spoke setup, if you
lose the hub, then you lose everything, that is just the way it is....it
doesn't really have anything to do with VPN wizards, DNS or FQDNs. The hub
is the "single point of failure".
We have the same VPN based Hub & Spoke setup with about 20+ sites from all
over the US. If the central "hub" (our Corp HQ) goes down, then the story is
simply over. They way we avoid trouble is to just not depend on the Hub for
everything. Our DNS, WINS, Internet connection, Mail Server (Exchange), Web
Server are are handled independently by us. Every site is pretty much
autonomous, we only use the "Hub" for things specific to what we need the HQ
for. If they are down, we just wait till they pick up the pieces and get
going again. We'll survive without them until they do. Communication between
sites in the form of Email still works because each site has thier own
locally maintained Mail Server and Internet Connection and so email never
depended on the "hub" to start with.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"SizzleMaster" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have a hub and spoke configured gateway<>gateway VPN WAN where each
spoke
> end connects to the hub via Win Server 2003 RRAS and ISA erver 2001 packet
> filters. If the hub goes down, the spokes can't talk to each other
becuase
> the ISA VPN wizard requires fixed IPs to setup the connection.
>
> Is there any way to hard wire them with fixed routes to their FQDNs? I'm
> using dynamic DNS to resolve the FQDNs.
>
> Thanks for ANY assistance.
>
>