Bug 56660 - /etc/resolv.conf search for nisdomain.
Summary: /etc/resolv.conf search for nisdomain.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: dhcpcd
Version: 7.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Elliot Lee
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-23 16:58 UTC by Per Starbäck
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-11-23 16:58:36 UTC
Embargoed:


Attachments (Terms of Use)

Description Per Starbäck 2001-11-23 16:58:30 UTC
Description of Problem:


Version-Release number of selected component (if applicable):
dhcpcd-1.3.18p18-13

How Reproducible:
Always.

When I boot using dhcp and the dhcp server tells the client what nis-domain
to use, that is used for updating "domain" and "search" in /etc/resolv.conf.

I expected it to only use (dns) domain-name for /etc/resolv.conf.

The dhcp server I use is dhcp-2.0p15-4 on RH7.1.  I don't think there is
anything strange with the answer it gives.  The client's
/etc/dhcpc/dhcpcd-eth0.info includes both a "DOMAIN=..." and a
"NISDOMAIN=..." line with correct values.

Comment 1 Elliot Lee 2001-12-31 20:24:48 UTC
As of dhcpcd-1.3.21pl1, the 'domain' is not written out, and the 'search' path
includes both the DNS domain and NIS domain. For some people (such as myself)
this is needed, and for the others, it does not hurt anything beyond a
negligible performance loss, so I will leave it as-is.


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