Bug 11157
Summary: | incorrect setting of dns search domains | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Eric Jorgensen <alhaz> |
Component: | linuxconf | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | ||
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: | 2000-05-02 18:24:35 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
Eric Jorgensen
2000-05-01 20:13:12 UTC
This is not a bug. There may in fact be situations where the local domain should not be searched (for example, the "dsl.[myisp].net" domain). If you leave the search list blank, the default domain is used automatically. OK, maybe this is a cosmetic / cognitive thing. Probably just my QA experience screaming "This is OK for me, but it's going to cause customer support issues". If I'd thought more about it i could have come to that conclusion, but visually with the fields marked "optional" it looks like they're intended to be additional. I could swear I've used an ip stack that interpreted resolv.conf differently but i can't remember which (os/2 or something) |