Subject: Re: can't resolve named hosts
From: Ben Stanley (bds02@uow.edu.au)
Date: Sun Mar 03 2002 - 21:21:00 MST
There are two DHCP clients:
dhcpcd
pump
pump does a better job than dhcpcd (I only read the rpm packaging
blurb). Alternatively, you can do kernel level DHCP client
configuration, but you don't need to do that unless you're running nfs
root. It`s not as flexible as the userspace daemons, so it's not
recommended unless you really need it.
Ben.
Justin Christopher wrote:
> The "server" is an Apple Airport base station, so I don't have lots of
> options there. What's "pump"?
>
> On Sunday, March 3, 2002, at 07:53 PM, Jer_57 wrote:
>
>> Hello Justin,
>>
>> Actually, using pump as the client and having a properly setup DHCP
>> server, the DNS settings are passed on and picked up correctly. I
>> have this running on serveral YellowDog systems as well as RedHat
>> and HardHat systems. If the server isn't setup to pass on gateway
>> and DNS settings, then the client won't set them up properly when it
>> gets it's IP. Might want to make sure your dhcpd.conf file is setup
>> correctly on the server.
>>
>> jer
>>
>> Sunday, March 03, 2002, 8:20:17 PM, you wrote:
>>
>>
>> JC> On Saturday, March 2, 2002, at 01:43 PM, Keary Suska wrote:
>>
>>>> on 3/2/02 2:30 PM, jchristopher@takenote.net purportedly said:
>>>>
>>>>> I connect to the internet via an Airport Base Station that hands out
>>>>> IPs
>>>>> via DHCP at boottime. Works fine for Windows and OS X clients, both
>>>>> wired and wireless.
>>>>>
>>>>> Under YDL 2.1 on my iBook, I can ping numeric hosts on my LAN,
>>>>> ping the
>>>>> IP of the base station, and ping external internet hosts
>>>>> (206.117.xxx.yyy, etc. ). But named hosts like mail.mydomain.com or
>>>>> www.yahoo.com just time out and never connect.
>>>>
>>>>
>>>> The answer is fairly obvious--it's a DNS problem. Check your
>>>> resolv.conf
>>>> file to make sure valid entries are made. Depending on how your DHCP
>>>> server
>>>> works, you may have to specify DNS hosts manually.
>>>>
>>>> Keary Suska
>>>> Esoteritech, Inc.
>>>> "Leveraging Open Source for a better Internet"
>>>
>>
>>
>> JC> Well, since both OSX and Windows hosts can get IPs and resolve hosts
>> JC> without the need to hard code in a DNS server, why should it be
>> that way
>> JC> under Linux? Should not YellowDog get the DNS server on the fly
>> from the
>> JC> DHCP server?
>>
>> JC> Of course I can hard code valid DNS servers into resolv.conf -
>> but that
>> JC> kind of defeats the point of getting everything from DHCP... what
>> if my
>> JC> ISP decides to switch the IP of their DNS servers?
>>
>> JC> Clients that honor the "dynamic" DNS will keep working, and the
>> JC> hard-coded DNS server IPs I feed YellowDog will fail!
>>
>>
>> --
>> Best regards,
>> Jer_57 mailto:jer_57@yahoo.com
>>
This archive was generated by hypermail 2a24 : Sun Mar 03 2002 - 21:33:21 MST