Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!pt.cs.cmu.edu!f.word.cs.cmu.edu!eht
From: eht@f.word.cs.cmu.edu (Eric Thayer)
Newsgroups: comp.sys.next
Subject: Re: host name resolution under 1.0
Message-ID: <6271@pt.cs.cmu.edu>
Date: 25 Sep 89 20:34:00 GMT
References: <6251@pt.cs.cmu.edu> <15940@pollux.UUCP>
Organization: Carnegie-Mellon University, CS/RI
Lines: 34

In article <15940@pollux.UUCP> merlin@smu.UUCP (David Hayes) writes:
> If you try to resolv "x.y", the resolver would be required to make multiple
> queries with varying bits of the current host's domain appended.
>  Most of these would result in an error result from the name server, because
> the resulting host name "x.y.dept" does not exist.

I'd agree if, for example, your machine was V.W in X.Y.Z and you tried names
like:
	V.W
	V.W.X
	V.W.X.Y
	V.W.X.Y.Z

but, if you tried it inverted like

	V.W.X.Y.Z
	V.W.Y.Z
	V.W.Z
	V.W

I assume that most names would be resolved rather quickly if the the names that
are to be resolved, by in large, are in a subdomain of the domain in
/etc/resolv.conf.

A problem arises when a fully qualified name is put in the system.  However,
if you treat all names as fully qualified (if they have a dot in them), then
use the second scheme for resolution, maybe this would be worth the cost in
extra nameserver requests.



-- 
Eric H. Thayer      School of Computer Science, Carnegie Mellon
(412) 268-7679      5000 Forbes Ave, Pittsburgh, PA 15213