From owner-freebsd-current Thu Nov 30 12:48:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from munin.odin-corporation.com (munin.odin-corporation.com [216.233.173.18]) by hub.freebsd.org (Postfix) with ESMTP id EE5FC37B400 for ; Thu, 30 Nov 2000 12:48:32 -0800 (PST) Received: from odin-corporation.com (localhost [127.0.0.1]) by munin.odin-corporation.com (8.11.1/8.11.1) with ESMTP id eAUKlEf87758; Thu, 30 Nov 2000 14:47:14 -0600 (CST) (envelope-from lars@odin-corporation.com) Message-ID: <3A26BCD2.70DB75E@odin-corporation.com> Date: Thu, 30 Nov 2000 14:47:14 -0600 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: Andrea Campi Cc: current@freebsd.org Subject: Re: environment variable for resolv.conf anyone? References: <3A26B182.8717E963@odin-corporation.com> <20001130210006.A372@webcom.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Yes I have thought of that. I ran into a few issues that I thought made the solution cumbersome. Perhaps you solved these in a way that makes them dissapear? 1) Need to always use fully qualified names (only a problem when there are duplicates) 2) Need to bounce named a lot to avoid having records for networks that are not currently connected to. (perhaps sufficient to edit search line in resolv.conf each time a network gets added/deleted.) 3) If the remote network consists of lots of subdomains the named config becomes rather large. Lars Andrea Campi wrote: > This is my only message in this thread, it's out of topic. > > On Thu, Nov 30, 2000 at 01:58:59PM -0600, Lars Fredriksen wrote: > > Hi, > > > > I find myself connected to multiple networks and domains all the time, > > and was wondering if anyone has solved (without using a chroot > > environment) using a different resolv.conf for different shells? > > Have you thought about running your own non-authoritative DNS? If you use > djbdns, this gives you the added benefit of being able to easily specify > which DNS is authoritative for special, local domains. In general, having > your local, caching-only (in bind parlance) DNS gives you better security > and flexibility, and it's very easy to maintain. All of my machines, clients > and servers, run like that, and I never had any problem. > > Bye, > Andrea > > -- > Intel: where Quality is job number 0.9998782345! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message