Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 4028 - pump behaving differently than dhcpcd
Summary: pump behaving differently than dhcpcd
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pump
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Elliot Lee
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-07-14 12:51 UTC by wlf
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2001-07-16 13:32:16 UTC

Attachments (Terms of Use)

Description wlf 1999-07-14 12:51:54 UTC
In Red Hat 5.2, the domain-name option information returned
by the DHCP server was entered by the dhcpcd client into the
/etc/resolv.conf as a "domain" record.

In Red Hat 6.0, the pump client daemon enters the "domain-
name" option into /etc/resolv.conf as a "search" record.

This results in a behavior change that might cause a 6.0 host
to not be able to resolve names that a 5.2 host could.

In our case, our DHCP server includes the global option:

        option domain-name "";

Under 5.2, the first line of the /etc/resolv.conf then read:


Under 6.0, the first line now reads:


On the host "", the short name "weeks"
resolved to the local host under 5.2. Under 6.0, it does not
resolve at all.

What was the rationale for changing the record in /etc/
resolv.conf from "domain" to "search"?

How is one supposed to get previous behavior back?

Comment 1 Elliot Lee 2001-07-16 18:53:13 UTC
Ancient bug, closing.

The 6.0 behaviour looks correct - the 'domain' keyword is rather obsolete...
Perhaps there is a glibc bug - if this problem still exists in 7.1, please file
a new report against that release.

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