"DHCP set the hostname"
Carl Karsten
carl at personnelware.com
Thu Mar 1 02:58:39 UTC 2007
Thanks. Not quite as definitive as I had hoped for, but good enough.
Next Q: what are the implications of multiple machines with the same hostname?
In other words: does it matter if they are all left set to localhost.localdomain?
Carl K
Tim Peiffer wrote:
> A read of the manual page for dhcp-option(5) and dhclient-script(5) is
> useful. An excerpt from the man page says:
> option host-name string;
>
> This option specifies the name of the client. The name may
> or may
> not be qualified with the local domain name (it is preferable
> to use
> the domain-name option to specify the domain name). See
> RFC 1035
> for character set restrictions. This option is only
> honored by
> dhclient-script(8) if the hostname for the client machine
> is not
> set.
>
> The use of the host-name specified is optional and depends upon how the
> client is configured. Now the next logical question, is how does this
> work in Winderz?
>
>
> Carl Karsten wrote:
>> host-name is optional, right?
>>
>> I am sure I know the answer, but can't find support for it.
>>
>> This is for a olpc bugreport that goes like this:
>>
>> cjb: doesn't DHCP set the hostname, though?
>> CarlFK: it can, but from what I have seen dhcp doesn't always happen
>> CarlFK: and it isn't guaranteed
>>
>> cjb: if dhcp doesn't happen, we're not on a network and don't care that we don't
>> have a unique hostname.
>>
>> Carl K
>>
>
>
>
More information about the dhcp-users
mailing list