Bug 72087
Summary: | Altered dhcp behaviour sets hostname by default, means Gnome 2 won't start with many ISPs | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Mike MacCana <mikemaccana> |
Component: | dhcpcd | Assignee: | Elliot Lee <sopwith> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | null | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-08-26 15:03:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mike MacCana
2002-08-21 02:02:29 UTC
Some DSL hardware router/firewalls such as NetGear RT314 also do this, and for a "good" reason: they don't provide DNS, only DHCP server. Even if you [try to] tell it your prefered hostname in your DHCP request, the router/firewall just gives you an IP4 with a name such as "dhcppc5". And even if the router/firewall were to honor your prefered hostname, it might be restricted in length so that a FQDN would be too long in most cases. So, it is better to let the HOSTNAME in /etc/sysconfig/network be the default, and override it only with explicit user OK. If you are getting a bad hostname, the DHCP server is in error... It seems that there needs to be an option of not setting the hostname (which I need to add), but the default of following the instructions from the DHCP server is correct. *** Bug 72622 has been marked as a duplicate of this bug. *** *** Bug 72622 has been marked as a duplicate of this bug. *** HOSTNAME= takes precedence in 3.0pl1-8 |