On Wed, Dec 15, 2010 at 17:52, Russell Johnson <[email protected]> wrote:
> On Dec 14, 2010, at 10:46 PM, Michael C. Robinson wrote:
>
>> An inferior solution is to set my Netgear RP614v4 router to use a DSL
>> based static ip subnet as the source for DNS queries. This will work
>> unless the DSL is down. Oops! I need a better solution.
Getting any degree of redundancy with multiple links is really hard, sorry.
The easy answer would be to purchase one of the end-user routers
(often sold for small businesses) that offer the ability to use
multiple Internet connections, and often 3G these days, with fail-over
or even load balancing.
The not-buying-a-solution answer is that you should probably run your
own DNS server on one of your systems internally, and delegate it the
responsibility of communicating with the outside world. That would
give you the same advantages as running the widget with a DNS cache,
without the penalties of inflexibility.
You could also just have your DHCP server tell the clients to talk
direct to OpenDNS and bypass any local DNS caching. :)
> Regardless of everything else.
> 1> What is the problem you are trying to solve?
He wants multiple Internet connections to let him still connect when
one is down.
> 2> Why does it matter than DNS isn't working when the connection is down?
> Where will you be going when the DSL is down? If it's internal, then you need
> a DNS inside your network. If you are resolving external addresses, you don't
> need to know until the DSL is back up.
That would defeat the purpose. ;)
Regards,
Daniel
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
