All of lore.kernel.org
 help / color / mirror / Atom feed
From: /dev/rob0 <rob0@gmx.co.uk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] need help on multiple isp routing
Date: Mon, 03 Oct 2005 15:38:12 +0000	[thread overview]
Message-ID: <200510031038.12300.rob0@gmx.co.uk> (raw)
In-Reply-To: <000901c5c4c8$d4a518a0$1000a8c0@naksitrallid.dyn.ee>

On Monday 2005-October-03 09:37, Anonymous wrote:
> configure is how to make those 2 links to use their own DNS servers,

Why?

> as ISP's1 servers do not answer queries from ISP's2 ip address and

So? They're answering queries from your ISP1 address, no? Is this a 
problem?

> vise versa. i run BIND (as caching and also for my local zone) on my
> router configured to forward requests to ISP's1 DNS servers. i really
> don't want to run 2 copies of BIND with forwarders of ISP2 as the
> only difference in configuration. would anybody come up with a more
> elegant solution on that issue? i'm sure it is not nice to specify

Just don't use forwarders at all. wget the latest root hints file or 
just use what you have, for "type hints" for the "." zone.

Forwarding is rarely a good idea. It gains you nothing. You won't 
increase the load on the root servers.

> both ISP's servers as forwarders for a single server as the server
> itself uses default gateway of ISP1.

So this is not a problem, but still, forwarders are not helping you.

> and then about services 
> installed on a router machine itself - ftp, www. they do not seem to
> listen on ISP's2 ip. any solution besides configuring virtual
> servers?

I prefer Julian's approach to dual gateway routing ... his routes patch 
and the nano.txt HOWTO. That provides more of what people tend to want 
from multiple ISP connections in a more transparent way. All services 
use both links equally (or as weighted.)

I'm sure there are situations in which splitting traffic by service or 
destination makes sense ... just not at my 3 dual-ISP sites.
-- 
    mail to this address is discarded unless "/dev/rob0"
    or "not-spam" is in Subject: header
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2005-10-03 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29  7:37 [LARTC] need help on multiple isp routing Anonymous
2005-09-29  9:23 ` Anonymous
2005-09-30  6:32 ` hareram
2005-09-30  7:35 ` Anonymous
2005-09-30  7:55 ` hareram
2005-10-01 19:13 ` Anonymous
2005-10-03 14:37 ` Anonymous
2005-10-03 15:38 ` /dev/rob0 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200510031038.12300.rob0@gmx.co.uk \
    --to=rob0@gmx.co.uk \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.