This bug was fixed in the package dhcp3 - 3.1.3-2ubuntu3
---
dhcp3 (3.1.3-2ubuntu3) lucid; urgency=low
* debian/dhclient-script.linux: Fix regression in host_name option
handling, so that it's always honored when /etc/hostname is not set,
fixes LP: #537978, #482313, #90388,
** Tags added: regression-release
--
hostname supplied by dhcp server is not used
https://bugs.launchpad.net/bugs/90388
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bug
Hello?? It used to work in Hardy!!!
Therefore either a newer version of dhcp3-client or network-manager or a
change to the default configuration by the ubuntu developers must have
caused this to stop working. The ability to centrally manage large
numbers of workstations includes the ability to set
I've just tested this on 9.10 server. Just create the file '/etc/dhcp3
/dhclient-exit-hooks.d/hostname' with the contents:
if [[ -n $new_host_name ]]; then
echo "$new_host_name" > /etc/hostname
/bin/hostname $new_host_name
fi
Works!
--
hostname supplied by dhcp server is not used
https://bu
It's a shame Ubuntu can't get hostname from DHCP server. It's 2010. Bug is
almost three years old.
But before I read the comments I didn't realize that X server may be affected
by hostname change.
Any thoughts how can this be handled? I really want this fixed.
I don't use NetworkManager, for me
Another approach might be to set "/etc/hostname" to the value from DHCP
server, and leave the current hostname alone. That would set the host
name to correct value at next boot, without any clash with netowork
manager behaviour or a running X [ and hopefully the name would not
change between reboot
Hi all,
well, after reinstallation an reconfiguration of the full system, it now
works... The only thing i did is to remove the file /etc/hostname
(without believing in this action) and it's ok now... So now I can
deploy Sorry for that...
--
hostname supplied by dhcp server is not used
https
Hello...
I was so happy finding this script but it didn't work for me... I tried to use
it on karmic today. First I did like on hardy, using a hostname file empty (it
was well working), but it seems it prevents the eth0 interface to be brought up
networkmanager and even if declared in /etc/netw
Gökdeniz Karadağ - your solution doesn't work on Ubuntu 8.10.
I had completely removed NetworkManager and put correct configuration lines
into the interfaces file (network connection is working fine) and this did not
changed anything.
Your previous solution did the trick. So thank you very much
Hi,
dhclient.conf does not need modifications.
On ubuntu, /etc/network/interfaces file has only loopback interface,
This causes the eth0 interface to be down until glorious NetworkManager kicks
in.
Add the following lines to /etc/network/interfaces as a fix
auto eth0
iface eth0 inet dhcp
--
h
Tx Gökdeniz,
Can you be more specific about the other modifications you added in
dhclient.conf and or interfaces ? I added the script without touching any other
conf files and do not get my hostname from the dhcp server.
--
hostname supplied by dhcp server is not used
https://bugs.launchpad.ne
We solved it by putting "hostname $new_host_name" into a file at
/etc/dhcp3/dhclient-exit-hooks.d/
Thanks Thomas for the tip.
default host-name "NO-NETWORK" did not work, when network was not
available hostname was "none" (or blank, i'm not sure) as jason said.
Booting the machine took ages, so
12 matches
Mail list logo
