Bug 10634 – search missing in resolv.conf

Bug 10634 - search missing in resolv.conf

Summary:	search missing in resolv.conf

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	installer (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael Fulbright
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-04-07 10:53 EDT by Michael Redinger
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-04-11 14:28:28 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Michael Redinger 2000-04-07 10:53:32 EDT

Right after installation, resolv.conf does contain the nameservers I
entered during (graphical) installation, but search [domain] is missing. No
wonder - the installer doesn't ask about this ...
Therefore I suppose this is not easy to fix, you would have to change the
install disks. However, a more trivial fix would be to check if the
hostname entered is fully qualified (contains a dot). If yes, skip the host
part and enter the rest as search.

Comment 1 Jay Turner 2000-04-11 12:38:59 EDT

What did you enter in the "Hostname" field in the graphical installation??  The
intent was that the user enter the FQDN here, and that would be parsed to give
the correct entry in /etc/resolv.conf.

Comment 2 Michael Redinger 2000-04-11 14:28:59 EDT

Ok, that is it.
Changed to NOTABUG - although I'm not quite sure about this ... the former
method - a field were you had to enter the search domain - was IMO
much more obvious ...

Comment 3 Daniel Roesen 2000-04-14 19:51:59 EDT

ACK
The input box should clearly state that you have to enter a *FQDN*.

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