From owner-freebsd-questions Thu Jun 20 20:15:45 2002 Delivered-To: freebsd-questions@freebsd.org Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161]) by hub.freebsd.org (Postfix) with ESMTP id 1D3F037B419 for ; Thu, 20 Jun 2002 20:15:40 -0700 (PDT) Received: from ih2mail.ih.lucent.com (h135-1-241-39.lucent.com [135.1.241.39]) by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g5L3FbF04860; Thu, 20 Jun 2002 23:15:37 -0400 (EDT) Received: by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id WAA19966; Thu, 20 Jun 2002 22:15:36 -0500 (CDT) Date: Thu, 20 Jun 2002 22:15:36 -0500 (CDT) Message-Id: <200206210315.WAA19966@ih2mail.ih.lucent.com> From: shawnlkennedy@lucent.com (Shawn L Kennedy) To: shadow@CPE0004761ac738-CM00109515bc65.cpe.net.cable.rogers.com Subject: Re: DHCP/DNS question Cc: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> > In /etc/rc.conf you probably have something like this: >> > >> > ifconfig_xl0="DHCP" >> > >> > Can you try to put this : >> > >> > send host-name "your-host-name" >> > >> > into /etc/dhclient.conf >> > >> > Hope that's what you need! >> >> Hi Miro, >> >> A good shot, but it didn't seem to do anything usefull. >Hi Shawn, > >Thanks ;-) but not very helpfull.. It was worthy try!! >> dhclient.leases did not change (no host-name in the file). > >This means that the problem, probably, is not that your >DHCP client is not sending your host name as you DNS guy said. >I saw that you have two DNS servers: domain-name-servers and >netbios-name-servers... >Can you try to ping your host 'name' but from host that have only the >domain-name-servers not both of them. You can enter them manually. when I issue the nslookup, the only machine that answers back is the DNS machine. no other machine gives an answer to the nslookup. A ping gives me back a "unresolved host name" error from the Solaris box. A Windows box, the ping also fails on the machine lookup. The FreeBSD box also comes back with a "unresolved host name" error. The only machines I have access to to perform the ping is my FreeBSd box, a Win2K box and a Solaris Enterise box running Solaris 2.8. Do you have any guidance? >Is your network M$ Active Directory Services enabled? Yup, but the DNS and DHCP boxes are Solaris Enterprise boxes running (I think) Solaris 2.8. They did take a recent update to Bind (version 8). Company also has WINS boxes that I think they use for the M$ crap. Network is a hetrogenous comglomeration of Sun Workstations (they have fixed IPs), Wintel boxes running M$2K and Linux boxes. As far as I know, I think I'm the only FreeBSD guy here. :-( >> The DNS lookup still shows an invalid name. >>From which DNS server (the server IP) from netbios-ones or others? DSN machine(s) - DHCP machine listed first, then DNS machine liste second in dhclient.leases in the domain-name-servers line. The netbios-name-servers are the WINS machines. >If everithing with the 'standart' DNS-DHCP server is OK you must be able >to ping your host name from non Windows host. (You said something about >Linux host - what DNS servers it is using. They use the same cloud/DHCP/DNS machines. >If you cannot ping your host name from M$ Windows hosts, you may need >to add static entry as Adam said into M$ DNS Server pointing >to your IP static adress. As far as I know M$ DNS servers are not >exectly 'UNIX' compatible because of ADS 'extensions' or whatever they say. This would be a bummer - the DNS guy said it should work. He's a linux guy and I keep trying to show folks that FreeBSD is "better" :-). This is not stating my case very well... :-( I might try firing up an analyer to watch the packets and see what the DHCP client is really sending. I have a very nice Agilent Internet Advisor sitting next to me that should do the trick. I'm at home now, so it would have to wait until morning. Also, I have a 4.5 box that I had decommissioned (I traded up in boxes!!) and will plug that in and see if that one still works. If so, I have to figure out why next..... Thanks for all your help, Shawn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message