From owner-freebsd-questions@FreeBSD.ORG Sat Apr 28 17:35:01 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1281916A400 for ; Sat, 28 Apr 2007 17:35:01 +0000 (UTC) (envelope-from beech@alaskaparadise.com) Received: from stargate.alaskaparadise.com (7-137-58-66.gci.net [66.58.137.7]) by mx1.freebsd.org (Postfix) with ESMTP id 247E513C45A for ; Sat, 28 Apr 2007 17:35:00 +0000 (UTC) (envelope-from beech@alaskaparadise.com) Received: from localhost (localhost [127.0.0.1]) by stargate.alaskaparadise.com (Postfix) with ESMTP id A7E647D97; Sat, 28 Apr 2007 09:34:58 -0800 (AKDT) From: Beech Rintoul Organization: FreeBSD Port Maintainer To: L Goodwin Date: Sat, 28 Apr 2007 09:34:51 -0800 User-Agent: KMail/1.9.6 References: <39066.55121.qm@web58113.mail.re3.yahoo.com> In-Reply-To: <39066.55121.qm@web58113.mail.re3.yahoo.com> X-Face: jC2w\k*Q1\0DA2Q0Eh&BrP/Rt2M,^2O#R07VoT98m*>miQF9%Bi9vy`F6cPjwEe?m,)=?utf-8?q?2=0A=09X=3FM=5C=3AOE9QgZ?="xT3/n3,3MJ7N=Cfkmi%f(w^~X"SUxn>; 27NO; C+)g[7J`$G*SN>{<=?utf-8?q?O=3Bg7=7C=0A=09o=7D=265A=5D4?=@7D`=Eb@Zs1Ln814?]|k@'bG=.Ca"[|8+_.OsNAo8!#?4u MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704280934.54852.beech@alaskaparadise.com> Cc: freebsd-questions@freebsd.org Subject: Re: DHCP client configuration on FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: beech@alaskaparadise.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Apr 2007 17:35:01 -0000 On Saturday 28 April 2007, L Goodwin said: > --- Beech Rintoul wrote: > > On Friday 27 April 2007, L Goodwin said: > > > When I ran the DHCP client configuration tool on > > > FreeBSD 6.2, it added a new hostname variable to > > > /etc/rc.conf below existing the hostname var (it > > > did not remove or comment-out the old hostname > > > variable). > > > The NEW hostname includes the ISP's domain name: > > > hostname="dhcppc0." > > > > > > This hostname differs from the hostname listed in > > > the router's DHCP table "dhcpp0" (no domain name). > > > It also shows unique IP addresses and MAC > > addresses > > > > for all hosts on the LAN. > > > > > > I can ping the IP address assigned to the FreeBSD > > > system, but ping and net lookup fail when its > > > hostname is specified (both with and without the > > > domain name). > > > > > > Questions: > > > 1) Why did the hostname get changed (does not > > > occur for Windows clients)? > > > 2) Why does the hostname in /etc/rc.conf contain > > > the DNS domain name? > > > > FreeBSD uses the FQDN (fully qualified domain name) > > as the hostname. > > Example: hostname= "yourmachine.yourdomain.com" > > > > > 3) How do I resolve this problem? > > > > Unless you provide your own DNS that resolves your > > internal network and supersede dhclient with your > > domain name, DHCP will use the domain and DNS from > > your provider. Your windows boxes point to your > > isp's nameservers which have no records of your > > server or it's address. Therefore it can't resolve > > your machine's hostname. > > If you do provide your own internal name service you > > will also need to edit /etc/dhclient.config (see man > > dhclient.conf), and point your windows boxes to your > > DNS instead of your isp's. You can use a fictitious > > domain name internally, just make sure that the > > domain doesn't actually exist on the net. > > You can also use the FreeBSD IP address as a domain > > name on your windows boxes to connect. > > Is there a way to a) make dhclient use hostname > without a domain name appended, or b) make dhclient > instruct the DHCP server to append the domain name to > the hostname? You're confusing windows networking with "real" networking. If all you're trying to do is share files with the windows boxes, just put the machine name as hostname and don't worry what gets appended to it. Samba will handle the windows part of it (machine name and workgroup). Windows uses a different system to identify machines on it's network. Don't confuse a windows "domain" with a real domain they are different things. On a windows network you use samba to make the windows boxes "think" that the FreeBSD box is one of theirs and share files and printers. You can find detailed how-to's on samba's site. There is no need to ping by hostname unless you're running a server on the FreeBSD box in which case you need to setup real DNS or just use the FreeBSD IP as the hostname from windows. > > > Running bind requires a fairly steep learning > > curve, but there are simple nameservers in the ports > > tree that would probably better suit your needs. > > Are you referring to the built-in command in bsh that > lists/alters key bindings for the line editor? > I don't understand what bind has to do with any of this. I'm not talking about binding keys, what I was talking about is bind. That's a dns server already in the base system. If you want to freely resolve your machines by hostname and domain you probably need to set up a caching nameserver to resolve your internal network. And point all your machines at it. Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - Port Maintainer - beech@alaskaparadise.com /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html ---------------------------------------------------------------------------------------