Bug 540887 - Need to add DHCP_HOSTNAME
Status: CLOSED DUPLICATE of bug 488975
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-11-24 08:10 EST by Neal Becker
Modified: 2010-04-13 19:27 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-13 19:27:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Neal Becker 2009-11-24 08:10:41 EST
Description of problem:

nm-applet has a place to add DHCP_CLIENT_ID, but not DHCP_HOSTNAME.
When connecting eth0 to my corporate lan (which must use some sort of cisco box), without setting DHCP_HOSTNAME, my machine is not in DNS.

I have to manually add DHCP_HOSTNAME to /etc/sysconfig/network-scripts/if-cfg.eth0.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Quentin Armitage 2009-12-09 06:19:51 EST
See a lso bug #510253
Comment 2 Ferry Huberts 2009-12-31 11:11:30 EST
I can confirm this bug.

I have a dhcp/bind setup with ddns and when DHCP_HOSTNAME is not present in the client then the dns is not updated.

NetworkManager only allows setting of DHCP_CLIENT_ID, which then obviously breaks the ddns setup.

Manually adding the DHCP_HOSTNAME=... to the interface configfile is a temporary workaround but not very desirable
Comment 3 Ferry Huberts 2009-12-31 11:24:11 EST
actually grepping in /etc/sysconfig/network-scripts for DHCP_CLIENT_ID show NO matches. so the client id isn't used in the interface scripts.

maybe you confused client id with hostname / forgot to add support for client id to the interface scripts?
Comment 4 Dan Williams 2010-01-04 18:16:36 EST
I think most of the time NM should simply send your machine's current persistent hostname (which is set via HOSTNAME in /etc/sysconfig/network) to the DHCP server instead of having a text box for it.
Comment 5 Ferry Huberts 2010-01-05 04:54:42 EST
it should, but that's not what I'm seeing.
it's what the default nw i/f scripting does. NM apparently doesn't do this
Comment 6 Dan Williams 2010-01-16 19:46:27 EST
I'm not certain that NM currently does that actually, I'll need to check.  I suggest the behavior is this:

1) if a configured hostname is set in the connection profile itself, use that
2) otherwise, if send-hostname is set in /etc/dhclient-eth0.conf, use that
3) otherwise, if the system has a persistent hostname (from /etc/sysconfig/network) use that
4) otherwise, send no hostname

sound OK?
Comment 7 Ferry Huberts 2010-01-16 20:11:07 EST
seems ok and logical

I would go a bit further though:
0) add a bit of user interface to 'Edit connections' so that the user can configure the hostname that is sent, and persist this in the /etc/sysconfig/network-scripts/ifcfg-xxxx files. use the order you suggested to provide the default in case the variable is not set.
Comment 8 Dan Williams 2010-04-13 19:27:25 EDT

*** This bug has been marked as a duplicate of bug 488975 ***

Note You need to log in before you can comment on or make changes to this bug.