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.


don


----- Original Message -----
From: "Tom Diehl" <[EMAIL PROTECTED]>
To: "don fay" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, January 13, 2001 8:44 AM
Subject: Re: Fw: Could not reverse map address


> On Sat, 13 Jan 2001, don fay wrote:
>
> > no it wouldn't disable dns lookups - it would just not continue to try
if it
> > failed on first attempt; thus making you wait 30s or 60s or 2mins or
> > whatever the applications timeout is.  when you say 'problems telnetting
in'
> > i take it you mean it is  really slow and not that you simply cannot
login
> > as in connection refused (?).
>
> No, Immediately after entering the passwd and pressing enter I
> get "connection closed by foreign host". If I enter the machine in
/etc/hosts
> all is OK both with ssh and telnet.
>
> > i doubt your ISP has your 192.168. addresses
> > in their dns.
>
> You are correct. However the network in question is at work. All machines
> on that network have real ip addresses. 204.something. Everything seems
> to work normal except as described above.
>
> --
> ......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

Reply via email to