Date: Sat, 17 Mar 2001 14:15:39 -0500 (EST) From: Alex Pilosov <alex@acecape.com> To: Julian Elischer <julian@elischer.org> Cc: Nick Rogness <nick@rogness.net>, freebsd-net@FreeBSD.ORG, Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> Subject: Re: same interface Route Cache Message-ID: <Pine.BSO.4.10.10103171410450.8329-100000@spider.pilosoft.com> In-Reply-To: <3AB3B2FF.3A04B53C@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 17 Mar 2001, Julian Elischer wrote: > this will do what you want for OUTGOING packets. > incoming packets will probably all come in on one network. And to fix this, you play tricks with your DNS server :) A setup that I have at home: Domain with two listed nameservers (same machine, different IPs). BIND set up split-brained: two named.confs, one configured to listen only on IP on network A, the other on network B. Two zone files, one listing IPs on A, other on B. Result: BIND will reply with IPs that belong to the interface packet came in on. This provides load-sharing (nameservers for domain are usually queried randomly) and reliability (if one connection is down, everything still works, because the other "half" of nameserver is still running and giving out IPs on the correct interface). -- -- Alex Pilosov | http://www.acecape.com/dsl CTO - Acecape, Inc. | AceDSL:The best ADSL in Bell Atlantic area 325 W 38 St. Suite 1005 | (Stealth Marketing Works! :) New York, NY 10018 | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSO.4.10.10103171410450.8329-100000>