Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!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: hostname resolution
Message-ID: <6262@pt.cs.cmu.edu>
Date: 25 Sep 89 14:03:39 GMT
Reply-To: eht@f.word.cs.cmu.edu (Eric Thayer)
Organization: Carnegie-Mellon University, CS/RI
Lines: 17
Keywords:

Thanks to Pascal Chesnais and Doug Brenner for pointing out that, sadly,
this behavior is a documented feature and is part of the version of BIND that
NeXT uses.

The BIND appendix in the SysAdmin section of the manuals says that the
domain in the boot file (or resolv.conf file) is appended to names which
do not contain a dot in them (hence, F.WORD does not qualify even though
if BIND did append the domain it would find the name).

Workarounds exist, but a better BIND would be on my wishlist for 1.1.

...eric


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