On Mon, 15 Jan 2001, don fay wrote:
> Tom,
>
> it's possible (actually likely :) that i'm confused, but if your isp is your
> dns, and the network you are ssh'ing to is on the 192.168. network (not
> served by dns) then mebbe the simplest thing to do is fire up your own
> internal dns server - just don't allow connections or zone transfers from
> the 'outside' world.
Sorry for the confusion. The 192.168 network has nothing to do with the
problem. I use that at home. The problem is at work. Sooooooooo let me
explain the problem again. On the work network ALL machines have real ip
addresses. The nameserver is run by the ISP. The nameserver appears to
be working properly (as far as I can tell so I could be wrong). When I
ssh from one machine on the work net to another machine on the work net
if the machine I am sshing FROM is NOT in /etc/hosts on the TO machine
the machine I am sshing TO complains that the reverse name lookup is
failing (I do not have the exact error in front of me. I can get it if
needed). In addition if I use the same 2 machines and telnet in, telnet
closes the connection with no errors. If I put the from machine in the
to machine's hosts file all is well. Since this is causing problems with
both ssh and telnet I suspect this is some kind of DNS weirdness but I
do not know how to prove it.
Does this make the problem clearer?
--
......Tom ATA100 is another testimony to the fact that pigs can be
[EMAIL PROTECTED] made to fly given sufficient thrust (to borrow an RFC)
Alan Cox lkml 11 Jan 01
