Bug 11374 – search list only searches n-1

Bug 11374 - search list only searches n-1

Summary:	search list only searches n-1

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	bind (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Cristian Gafton
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-05-11 17:38 EDT by mike
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-05-23 16:32:39 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description mike 2000-05-11 17:38:12 EDT

if /etc/resolve.conf contains:
 search x.foo.com y.foo.com foo.com

and the host bar.foo.com is searched for via `nslookup bar', the search
fails.

if the line is modified to:
  search x.foo.com y.foo.com foo.com bogus.com

it works and resolves to `bar.foo.com'

Comment 1 nkadel 2000-05-23 16:32:59 EDT

I cannot duplicate this behavior: I've tried adding and deleting several
different domain entries, inside and outside of my local domain.

Are you sure you didn't have a typo in your domain entry?

Comment 2 Henri Schlereth 2000-07-12 18:50:44 EDT

Unable to duplicate this as well. As I would quote from the bind users-list "If you conceal the actual domain/machine names
we cannot even begin to help you or duplicate the error"

The normal accepted format for resolv.conf should be:
domain foo.com
search foo.com
nameserver 192.168.1.1
nameserver 192.168.1.2

Henri J. Schlereth

Note You need to log in before you can comment on or make changes to this bug.