| Summary: | pump behaving differently than dhcpcd | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | wlf |
| Component: | pump | Assignee: | Elliot Lee <sopwith> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | CC: | wlf |
| 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-07-16 13:32:16 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
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. |
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 "cert.org"; Under 5.2, the first line of the /etc/resolv.conf then read: domain cert.org Under 6.0, the first line now reads: search cert.org On the host "weeks.blue.cert.org", 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?