From owner-freebsd-questions@FreeBSD.ORG Sun May 22 18:45:15 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 3400D16A41C for ; Sun, 22 May 2005 18:45:15 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from forrie.com (forrie.hsd1.ma.comcast.net [24.147.45.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id C65C243D1D for ; Sun, 22 May 2005 18:45:14 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [192.168.1.99] (i-99.forrie.net. [192.168.1.99]) (authenticated bits=0) by forrie.com with ESMTP id j4MIj9SY073023 for ; Sun, 22 May 2005 14:45:09 -0400 (EDT) (envelope-from forrie@forrie.com) Message-ID: <4290D2B9.8060307@forrie.com> Date: Sun, 22 May 2005 14:43:05 -0400 From: Forrest Aldrich User-Agent: Mozilla Thunderbird 1.0.4 (Windows/20050516) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.hsd1.ma.comcast.net) X-MailScanner-LocalNet: Found to be clean Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: dhclient on FreeBSD-4.10 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2005 18:45:15 -0000 I'm having a problem with dhclient on FreeBSD-4.10, where I can't seem to get it to work properly. My ISP uses DHCP (Comcast), and I want to use my own "named" instance, opting to forward to theirs. According to the dhclient.conf manpage, I should be able to do either of these: interface "fxp0" { prepend domain-name-servers 192.168.1.1; } # supersede domain-name-servers 127.0.0.1; # supersede domain-name-servers 192.168.1.1; And I've tried both, they do not work. So, either I'm doing something wrong (very likely) or I've run across a bug. Thanks.