Bug 74304
Summary: | Will not boot into GDM for some DNS Hostnames after changed using neat. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | dfladebo |
Component: | net-tools | Assignee: | Phil Knirsch <pknirsch> |
Status: | CLOSED NOTABUG | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-09-27 14:42:37 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
dfladebo
2002-09-20 00:59:15 UTC
Ok, I believe this has something to do with my local network setup and the fact that I did not setup the machine names that wouldn't work (eg: home-linux as in the original report) as an alias in /etc/hosts. I have XP Pro. handing out the DHCP leases to the local network machines, of which the RH box is one. The reasons for this are long and varied, but it has to do with the setup for my ISP and the fact that their proprietary "modem" software runs only on Windows. Apparently when the original lease first expired for "home-tux" (there appears to be no way built into the XP "home-networking" stuff to control this), RH would no longer boot into GDM because it (GDM) couldn't properly use DNS to resolve the host name or something else odd like that. Anyhow, what I did to resolve this problem was edit the /etc/hosts 127.0.0.1 aliases entry to make sure that whatever I give the machine as a hostname is also an alias as well. I believe that it would be very helpful for non-network engineering types like me if neat would offer to modify the 127.0.0.1 aliases entry in the /etc/hosts file "automagically" when the hostname was changed on the DNS tab. Actually, that may be a great feature to add for network engineering types as well because from what I understand, even if you have a network and DHCP server that works really well, it may be a good practice to add the host name to the 127.0.0.1 aliases entry anyway for software that relies on hosts (?) Thanks for your patience with a newbie. Dave Fladebo OK, thanks for your report. We'll take you suggestions into consideration for future releases and versions of the tools. Read ya, Phil |