From owner-freebsd-stable@FreeBSD.ORG Mon Jun 5 22:09:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF26716D377 for ; Mon, 5 Jun 2006 21:48:56 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [209.89.70.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 768B743D46 for ; Mon, 5 Jun 2006 21:48:56 +0000 (GMT) (envelope-from lyndon@orthanc.ca) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by orthanc.ca (8.13.4/8.13.4) with ESMTP id k55LmnaX075807 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Jun 2006 15:48:49 -0600 (MDT) (envelope-from lyndon@orthanc.ca) Date: Mon, 5 Jun 2006 15:48:49 -0600 (MDT) From: Lyndon Nerenberg To: Damian Gerow In-Reply-To: <20060605195148.GJ99893@afflictions.org> Message-ID: <20060605154607.F74433@orthanc.ca> References: <44842282.6050409@veldy.net> <448428D8.5030501@orchid.homeunix.org> <20060605134049.GB99893@afflictions.org> <20060605131957.P74433@orthanc.ca> <20060605195148.GJ99893@afflictions.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on orthanc.ca Cc: freebsd-stable@freebsd.org Subject: Re: [OT] resolv.conf and dhclient X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2006 22:09:46 -0000 > And what happens when I'm connected at home, and need to view portions of > DNS that are only accessible to the wired network? Split DNS is a PITA. If your nameservers are smart enough they will see which path a query took, and act appropriately. Sadly, ours at work aren't. Yet. But as someone else mentioned, you've now gone beyond the realm of simple DHCP configuration. DHCP was never intented to deal with policy routing issues (at whatever layer of the stack). --lyndon