From owner-freebsd-current@FreeBSD.ORG Fri Jun 17 15:42:00 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7561916A446 for ; Fri, 17 Jun 2005 15:42:00 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3247643D49 for ; Fri, 17 Jun 2005 15:42:00 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.41.231] (Not Verified[216.133.140.1]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Fri, 17 Jun 2005 11:55:26 -0400 From: John Baldwin To: Brooks Davis Date: Fri, 17 Jun 2005 11:42:33 -0400 User-Agent: KMail/1.8 References: <200506161312.51857.jhb@FreeBSD.org> <20050616185022.GJ21733@odin.ac.hmc.edu> In-Reply-To: <20050616185022.GJ21733@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506171142.33489.jhb@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: New dhclient broke multiple domains in domain-name X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jun 2005 15:42:00 -0000 On Thursday 16 June 2005 02:50 pm, Brooks Davis wrote: > On Thu, Jun 16, 2005 at 01:12:51PM -0400, John Baldwin wrote: > > I'd very much like the old behavior restored if possible, or an > > alternative way to achieve the same result (multiple domains in the > > 'search' part of /etc/resolv.conf). Note that the old domain-name trick > > has worked all the way back to at least 4.1 and maybe even back in the > > 3.x days IIRC. > > I know about the issue and plan to fix it before release, but will not > get to it for another week. This is a really annoying feature because > it's widely supported, but clearly invalid based on reading the DHCP > spec. It's a bug that isc-dhcpd sends domain-name with spaces in it > since it violates the strict send, lenient accept rule. Note that the new dhclient binary is now violating the rule as well since it's not being lenient. :) At the very least, it could just throw out the domain-name and keep the rest of the lease rather than rejecting the entire lease offer. I've worked around it for now though and can wait a week or two to see what you come up with. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org