|Summary:||pump and dhcpcd handle the DNS search path differently|
|Product:||[Retired] Red Hat Linux||Reporter:||Peter Bowen <pzbowen+rhbeta>|
|Component:||dhcpcd||Assignee:||Elliot Lee <sopwith>|
|Status:||CLOSED WORKSFORME||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2001-08-09 20:11:31 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Peter Bowen 2001-08-08 23:43:35 UTC
When using pump as the dhcp client, it creates the search path for /etc/resolv.conf by first using the entire domain passed to it by the dhcp server, then progressivly stripping off leading parts until only the registered domain remains. With dhcpcd, it only puts the domain that is passed via dhcp in the search path. For example, my laptop at work is in the wdhq.scyld.com domain. Under pump, the search line was "search wdhq.scyld.com scyld.com", but with dhcpcd it is just "search wdhq.scyld.com" This is a regression from previous RHL versions that can have wide ranging effects. Anyone who expects a machine, that is not in their nth level domain, to be available via a simple host name will have problems.
Comment 1 Glen Foster 2001-08-09 20:11:26 UTC
This defect is considered SHOULD-FIX for Fairfax.
Comment 2 Elliot Lee 2001-12-28 20:27:21 UTC
My current resolv.conf has 'search redhat.com devel.redhat.com', so it appears to be fixed.