Bug 53081
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> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
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: | 2001-09-05 02:25:39 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
Joshua Jensen
2001-09-03 12:42:58 UTC
This is probably a dupe of this issue, it comes up from time to time. 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 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). 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. |