Bug 128900
Summary: | resolver seems to give up too easily | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | redhat-bugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 09:04:33 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
Michal Jaegermann
2004-07-30 22:33:26 UTC
The values used are good defaults. Users can change them by using options timeout:N attempts:M in resolv.conf. Just make sure dhcp does not destroy the file, but keeps the options. There will be noo glibc change. > Just make sure dhcp does not destroy the file ...
So how do you propose to do that, say, on a laptop which frequently
moves between different networks? Effectively you tell "fire
up an editor on every change and modify /etc/resolv.conf one
way or another". Besides the problem does not seem to be a timeout
or a number of attempts but that a name server got too many
hosts in a response.
|