Red Hat Bugzilla – Bug 385211
NetworkManager fails to honor send-hostname for DHCP
Last modified: 2008-09-29 22:49:14 EDT
Description of problem: My network uses a Fedora 6 machine as a DHCP and DNS
server. The DHCP server will hand out an address and send the hostname to the
DNS server so that I can ping the name and get the dynamic IP if it changes.
This worked great under Fedora 7. After I loaded F8 this stopped working.
NetworkManager does not send any hostname to the DHCP server. Somehow it is not
reading the /etc/dhclient-eth0.conf file.
If I disable the NetworkManager service and issue a "service network restart"
command, the hostname is sent and everything works normally. If I start
NetworkManager right after that, the hostname is not sent and my network is
screwed up again.
Version-Release number of selected component (if applicable): 0.7.0-0.5.svn3030.fc8
How reproducible: Always
Steps to Reproduce:
1. Set send host-name "hostname"; in /etc/dhclient-eth0.conf file.
2. Start NetworkManager, no hostname sent.
3. Stop NetworkManager, restart network service, hostname is sent.
Actual results: No hostname propagated to DNS server.
Expected results: Hostname pingable via DNS server.
Additional info: Other people have reported this as an issue, too, and I am
seeing the same thing on a clean Fedora 8 system on my same network.
Just a me too to get things going ;-)
BTW: I just tried a workaround mentioned in the gentoo wiki:
This did not work for me.
Does it work if you use /etc/dhclient.conf? That is the default dhclient config
Yes, it now works. Ugh, I should have done that sooner.
Depending on what is desirable behavior, you may wish to fix the
system-config-network packages since it was writing my desired hostname to the
interface specific file. Is this desirable or should NetworkManager be changed
back to read the interface-specific files?
NetworkManager will be changed to allow specifying the DHCP hostname and will
hand that off to dhclient as appropriate. Thanks for reporting that the
workaround worked for you!
*** Bug 401781 has been marked as a duplicate of this bug. ***
Bug 401781 may not be a duplicate because following the directions here does not
work for me even when placed in dhclient.conf.
Sorry, I caught myself. I was using tab completion. Yes, as dhclient.conf it
works. As dhclient-ethx.conf it doesn't work.
(In reply to comment #5)
> NetworkManager will be changed to allow specifying the DHCP hostname and will
> hand that off to dhclient as appropriate. Thanks for reporting that the
> workaround worked for you!
I realize this bug is old. Has this feature been added? How would one properly
(Will check rawhide)
Not yet, but you can get this functionality by adding the necessary bits to
/etc/dhclient.conf in the interim.
As I noted in my bug #401781, this was a regression in F7 or F8. We are now in
F9 and this bug still exists. Is this going to be fixed as promised? Has this
been forgotten about?
Why was this bug closed? Is there a more appropriate bug opened that requests
hostname support in NetworkManager? Can you (Dan) please link us to it? Should I
(or Trever) open a new bug requesting such? It has been far too long for such a
simple feature to go missing from *two* Fedora versions and multiple
It was closed because a workaround existed (editing the dhclient config file).
However, I have added support for honoring DHCP_HOSTNAME upstream, and it will
appear in a future update to NetworkManager. Thus, reopening the bug.
*** Bug 443815 has been marked as a duplicate of this bug. ***
This is now supported in svn4022 and later in f8-updates.