From owner-freebsd-hackers  Tue Sep 23 22:57:27 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA03865
          for hackers-outgoing; Tue, 23 Sep 1997 22:57:27 -0700 (PDT)
Received: from minor.stranger.com (stranger.vip.best.com [204.156.129.250])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA03853
          for <freebsd-hackers@freebsd.org>; Tue, 23 Sep 1997 22:57:16 -0700 (PDT)
Received: from dog.farm.org (dog.farm.org [207.111.140.47]) by minor.stranger.com (8.8.5/8.6.12) with ESMTP id XAA18257; Tue, 23 Sep 1997 23:02:47 -0700 (PDT)
Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id WAA02858; Tue, 23 Sep 1997 22:52:35 -0700 (PDT)
Date: Tue, 23 Sep 1997 22:52:35 -0700 (PDT)
From: Dmitry Kohmanyuk <dk@dog.farm.org>
Message-Id: <199709240552.WAA02858@dog.farm.org>
To: haskin@ptway.com (Brian Haskin)
Cc: freebsd-hackers@freebsd.org
Subject: Re: r-cmds and DNS and /etc/host.conf
Newsgroups: cs-monolit.gated.lists.freebsd.hackers
Organization: FARM Computing Association
Reply-To: dk+@ua.net
X-Newsreader: TIN [version 1.2 PL2]
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <34287531.FB18FE1F@ptway.com> you wrote:
> > > In article
> > <199709222122.RAA02406.kithrup.freebsd.hackers@lakes.dignus.com> you
> > write:
> > > > What's strange is that things on the gateway machine seem to
> > access
> > > >the local network (presumably using /etc/hosts) just fine.  It's
> > > >only rlogin's to the gateway machine from the internal network
> > > >that are causing the problem...
> > >

> I have also seen this going to a gateway. Both machines are running
> 2.2.2-RELEASE. Sorry I don't have any more info right now.

I have just tested this on two machines, client running 2.2-old and 
server running 2.2.2-R.  The bug is there, in rlogind or libraries it uses.

How to test: 
on server machine, put 127.0.0.1 into resolv.conf;  start named;
run
tcpdump -l -i lo0 -s 512 

now rlogin from your client.

see queries going to local nameserver on server machine.

in my case, these are:

# tcpdump -l -i lo0 -s 512                                                      tcpdump: listening on lo0
22:53:50.569483 localhost.1319 > localhost.domain: 31153+ A? dog.stranger.com. (34)
22:53:50.570916 localhost.domain > localhost.1319: 31153 NXDomain* 0/1/0 (87)
22:53:50.572942 localhost.1320 > localhost.domain: 31154+ A? dog. (21)
22:53:50.573687 localhost.domain > localhost.1320: 31154 NXDomain* 0/0/0 (21)

so, server tried to resolve names `dog.stranger.com.' - note the trailing 
dot - and then `dog.'   (dog is client machine;  stranger.com is domain).
None of those are in hosts, of course.

--
/earth is 98% full ... please delete anyone you can.