|Summary:||Installer gets DHCP'ing hostnames wrong|
|Product:||[Retired] Red Hat Linux||Reporter:||Joshua Jensen <joshua>|
|Component:||anaconda||Assignee:||Jeremy Katz <katzj>|
|Status:||CLOSED WONTFIX||QA Contact:||Brock Organ <borgan>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2001-09-05 02:25:39 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Joshua Jensen 2001-09-03 12:42:58 UTC
Description of Problem: I've done two installs or RC2 onto two different machines that are DHCP clients. One install was text-based via ftp, the the other a GUI install via NFS. The problems is that I was never prompted for the name of the machine, and after an otherwise good installation, the machine reboots and is "localhost.localdomain". /etc/sysconfig/network has HOSTNAME=localhost.localdomain, and /etc/hosts only has the one 127.0.0.1 line. It's annoying to boot to "localhost" named machines. Version-Release number of selected component (if applicable): RC2 How Reproducible: Install to a DHCP'ing host
Comment 1 Michael Fulbright 2001-09-04 18:36:02 UTC
This is probably a dupe of this issue, it comes up from time to time.
Comment 2 Jeremy Katz 2001-09-04 19:31:31 UTC
Do you have working reverse DNS for your DHCP'd hosts? With DHCP, we use the reverse dns given and otherwise fallback to localhost.localdomain. This is the most predictable and the most "correct" way to avoid breaking apps
Comment 3 Joshua Jensen 2001-09-05 02:25:35 UTC
Ah... that explains it. The two IPs that I used to install RC2 did not have reverse resolutions. But many IPs won't have PTR reverse-records... why not prompt for a hostname in those cases? Couldn't you just place the user-supplied hostname on the 127.0.0.1 line in /etc/hosts?: 127.0.0.1 localhost hostname localhost.localdomain My thinking behind this is that we don't always get the same IP if we use DHCP (reverse lookups aside), but we do always have loopback (which is the entire point of loopback).
Comment 4 Jeremy Katz 2001-09-05 17:06:28 UTC
This breaks several applications and we've been around this half a dozen other times. Answer -- if using dhcp, make dns work, otherwise fix /etc/hosts yourself and pick up the pieces of the apps that break :) It's, unfortunately, the best solution at the present time.