From owner-freebsd-questions@FreeBSD.ORG Fri Apr 16 13:41:06 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2481216A4CE for ; Fri, 16 Apr 2004 13:41:06 -0700 (PDT) Received: from gaff.hhhr.ision.net (gaff.hhhr.ision.net [195.180.9.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8AF843D1F for ; Fri, 16 Apr 2004 13:41:02 -0700 (PDT) (envelope-from ohoyer@ohoyer.de) Received: from gaff.hhhr.ision.net (ohoyer@localhost [127.0.0.1]) by gaff.hhhr.ision.net (8.12.11/8.12.11) with ESMTP id i3GKdrcY029843; Fri, 16 Apr 2004 22:39:53 +0200 (CEST) (envelope-from ohoyer@ohoyer.de) Received: from localhost (ohoyer@localhost)i3GKdq3L029840; Fri, 16 Apr 2004 22:39:53 +0200 (CEST) (envelope-from ohoyer@ohoyer.de) X-Authentication-Warning: gaff.hhhr.ision.net: ohoyer owned process doing -bs Date: Fri, 16 Apr 2004 22:39:52 +0200 (CEST) From: Olaf Hoyer Sender: ohoyer@gaff.hhhr.ision.net To: Jonathon McKitrick In-Reply-To: <20040416181258.GC91692@dogma.freebsd-uk.eu.org> Message-ID: <20040416222816.Y29786@gaff.hhhr.ision.net> References: <20040416175916.GB91692@dogma.freebsd-uk.eu.org> <20040416180648.72146.qmail@web14609.mail.yahoo.com> <20040416181258.GC91692@dogma.freebsd-uk.eu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-questions@freebsd.org Subject: Re: How do I eliminate resolver delay?? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Apr 2004 20:41:06 -0000 On Fri, 16 Apr 2004, Jonathon McKitrick wrote: > On Fri, Apr 16, 2004 at 11:06:48AM -0700, peter lageotakes wrote: > : FYI: If I remember correctly, running dhcpd > : overwrites the resolve.conf. > > That's what caused my problem. I need a way to restore it when using the > other network with assigned IPs. In your /etc/dhclient.conf you can use default/prepend statements, see dhclient.conf (5) You can rather finetune this, or have other ways: When you have @home some kind of server, have him also playing DHCP with assignment of gateway, dns etc. when it comes to dns, then you could setup named with split forward. So make sure that you have @home a different network than that from your work. Steps to do: in /etc/namedb, run ./make-localhost after /etc/hosts is populated with reasonable name for your box. make sure that a recent named.root is available. in named.conf: zone "." { type hint; file "named.root"; }; zone "0.0.127.IN-ADDR.ARPA" { type master; file "localhost.rev"; }; then comes the magic: //Aufsetzen des split forward fuer intern zone "0.168.192.IN-ADDR.ARPA" { type forward; forward only; forwarders { 192.168.0.1; }; }; zone "example.de" { type forward; forward only; forwarders { 192.168.0.1; }; }; Add forwarder statements where approp. I use this setup in a production environment on a box running nagios for monitoring several subnets, all VLAN with their own DNS in those VLANS... named will act as a caching nameserver only, when it comes to private VLAN, it will use those other DNS, anything not in those forwarders clauses will be resolved on his own, generating queries himself up to the root Nameservers. That would be the smart way of dealing with this, when you want, you could add a default forwarders statement to the ns of your ISP @home... HTH Olaf -- Olaf Hoyer ohoyer@gaff.hhhr.ision.net Fuerchterliche Erlebniss geben zu raten, ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist. (Nietzsche, Jenseits von Gut und Boese)