From owner-freebsd-questions@FreeBSD.ORG Sat Nov 29 11:59:14 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 1E45216A4CE for ; Sat, 29 Nov 2003 11:59:14 -0800 (PST) Received: from out009.verizon.net (out009pub.verizon.net [206.46.170.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8511A43FA3 for ; Sat, 29 Nov 2003 11:59:12 -0800 (PST) (envelope-from mike@pcmedx.com) Received: from duron.pcmedx.com ([4.46.22.189]) by out009.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20031129195911.LMQU15642.out009.verizon.net@duron.pcmedx.com>; Sat, 29 Nov 2003 13:59:11 -0600 Received: from localhost (localhost [127.0.0.1]) by duron.pcmedx.com (Postfix) with ESMTP id 1E72FB05D; Sat, 29 Nov 2003 11:59:11 -0800 (PST) Received: from mike (mike.pcmedx.com [192.168.240.244]) by duron.pcmedx.com (Postfix) with SMTP id 70DE8B05A; Sat, 29 Nov 2003 11:59:10 -0800 (PST) Message-ID: <007901c3b6b3$4eb14ef0$f4f0a8c0@pcmedx.com> From: "Mike Maltese" To: "FreeBSD Questions" References: <3FC8374F.2040301@comcast.net> Date: Sat, 29 Nov 2003 11:59:33 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd (http://www.amavis.org) and f-prot (http://www.f-prot.com) at pcmedx.com X-Authentication-Info: Submitted using SMTP AUTH at out009.verizon.net from [4.46.22.189] at Sat, 29 Nov 2003 13:59:11 -0600 Subject: Re: 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 19:59:14 -0000 > 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; > } Try ommiting the domain name. All you should really need in dhclient.conf is send host-name "pixie";