Ignore the original question.  I checked lapdog2&#39;s IP in a terminal that was logged into a different machine.  The ssh was using the right IP but getting this result and I cannot figure out why:<br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
larry@hammerhead:~$ ssh -v lapdog2<br>OpenSSH_5.8p1 Debian-1ubuntu3, OpenSSL 0.9.8o 01 Jun 2010<br>debug1: Reading configuration data /etc/ssh/ssh_config<br>debug1: Applying options for *<br>debug1: Connecting to lapdog2 [192.168.2.124] port 22.<br>
debug1: connect to address 192.168.2.124 port 22: Connection timed out<br>ssh: connect to host lapdog2 port 22: Connection timed out<br>larry@hammerhead:~$ <br></blockquote><br><br><div class="gmail_quote">On Fri, Jun 17, 2011 at 2:00 AM, Dazed_75 <span dir="ltr">&lt;<a href="mailto:lthielster@gmail.com">lthielster@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I tried to ssh from this machine to my laptop (ssh lapdog3) and find that ssh is somehow using an old IP instead of doing name resolution on th e name lapdog2 which now has a new lease on a different IP.  <br>
<br>1) How do I fix this?<br>
2) Why does ssh use an old, apparently, stored IP?<br clear="all"><font color="#888888"><br>-- <br>Dazed_75 a.k.a. Larry<br><br>The spirit of resistance to government is so valuable on certain occasions, that I wish it always to be kept alive.<br>

  - Thomas Jefferson<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Dazed_75 a.k.a. Larry<br><br>The spirit of resistance to government is so valuable on certain occasions, that I wish it always to be kept alive.<br>  - Thomas Jefferson<br>