From owner-freebsd-questions@FreeBSD.ORG Fri Nov 28 22:06:12 2003 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 04E9216A4CE for ; Fri, 28 Nov 2003 22:06:12 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9751843FBF for ; Fri, 28 Nov 2003 22:06:09 -0800 (PST) (envelope-from freebsduser@comcast.net) Received: from comcast.net (12-225-143-41.client.attbi.com[12.225.143.41]) by comcast.net (rwcrmhc13) with SMTP id <2003112906060901500pp14fe> (Authid: animotions); Sat, 29 Nov 2003 06:06:09 +0000 Message-ID: <3FC8374F.2040301@comcast.net> Date: Fri, 28 Nov 2003 22:06:07 -0800 From: K Anderson User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD Questions Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: dhclient.conf or DHCP 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: Sat, 29 Nov 2003 06:06:12 -0000 Hey folks, I have my freebsd DHCP server set up and working great. Well great for Windows clients, but not much so for BSD clients. Under the Windows clients I just set the host name and when the DHCP gets a request it dutifully does the job of assigning an IP address as well as putting in the proper DNS entries. I have tried the same for another BSD computer and it gets the IP address just fine but the request doesn't get passed on to DNS for updating. I tried the dhclient.conf being blank and then also tried putting in entries as suggested by man 5 dhclient. Any ideas on getting BSD to have the same behavior as Windows? This is what I have for dhcpd.conf option domain-name "squeaks.net"; option domain-name-servers msmouse.squeaks.net,204.127.198.4; server-name "msmouse"; server-identifier 192.168.100.250; key rndc-key { algorithm hmac-md5; secret "wouldn't you like to know"; }; zone squeaks.net. { primary 192.168.100.250; key rndc-key; } zone 100.168.192.in-addr.arpa. { primary 192.168.100.250; key rndc-key; } default-lease-time 600; max-lease-time 7200; # If this DHCP server is the official DHCP server for the local # network, the authoritative directive should be uncommented. authoritative; # ad-hoc DNS update scheme - set to "none" to disable dynamic DNS updates. ddns-update-style interim; # Use this to send dhcp log messages to a different log file (you also # have to hack syslog.conf to complete the redirection). log-facility local7; # No service will be given on this subnet, but declaring it helps the # DHCP server to understand the network topology. # This is a very basic subnet declaration. subnet 192.168.100.0 netmask 255.255.255.0 { range 192.168.100.1 192.168.100.99; next-server 192.168.100.250; option routers 192.168.100.105; use-host-decl-names on; } dhclient.conf is... interface "ed0" { send host-name "pixie.squeaks.net"; request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, host-name; script "/sbin/dhclient-script"; require subnet-mask, domain-name-servers; }