Bug 51138
Summary: | dhcpcd doesn't configure DNS | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Chris Ricker <chris.ricker> |
Component: | dhcpcd | Assignee: | Elliot Lee <sopwith> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
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: | 2002-04-15 16:14:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chris Ricker
2001-08-07 19:43:35 UTC
This defect is considered SHOULD-FIX for Fairfax I just encountered this problem on a third machine still true in RC2 Eek, old bug. Can anyone give a recent update on this? My machines work fine with dhcpcd, which is why I'm not able to do anything about it (can't reproduce -> can't fix). Still true with 7.2 gold Since dhcpcd configures DNS wonderfully for large groups of people (myself included), I pretty much need you to track this problem down in order to get any sort of fix in. If there are any particular conditions for reproduction, let me know. What information would you like? The only thing that is useful in producing a fix: a diagnosis of the problem. :) I would just run dhcpcd under gdb and put a breakpoint at the place where it writes out RESOLV_CONF, then step through that section and find out what input it is getting and what it is doing with that. If you want to do testing/debugging against the stuff under ftp://people.redhat.com/sopwith/1.3.21pl2-5/, that's my current package that has various fixes against the 7.2 one. Closing this -- the Qube2 running NetBSD has been retired after years of honorable duty as DHCP server, and I haven't reproduced this w/ its RHL replacement |