I'm trying to SSH to an Eee PC laptop running Debian on a network where hostnames are automatically registered with DNS via the DHCP server. The Eee PC laptop had run out of power and gone to sleep and now when it's booted up again, the Mac can't see it except for the
gaz:~ jeff$ ssh epc ssh: Could not resolve hostname epc: nodename nor servname provided, or not known gaz:~ jeff$ nslookup epc Server: 192.168.2.20 Address: 192.168.2.20#53 Name: epc.osnetwork Address: 192.168.2.139 gaz:~ jeff$ ssh epc.osnetwork ssh: Could not resolve hostname epc.osnetwork: nodename nor servname provided, or not known
ssh epc is how I normally access the Eee PC, but for some reason I think some part of OS X is caching a no-response despite the machine being online but I don't know how. I'm not even sure how to resolve this with any degree of certainty, I suspect a reboot will do it but for lack of a no-downtime solution I've just been using the IP address instead (which can still be obtained on the mac with
nslookup epc, which is the most baffling part).
If I SSH to another Mac that didn't try to contact the Eee PC while it was down, that Mac can SSH to it without problems, but when I go back to the original Mac it still can't reach the hostname.
Other non-Apple machines on the network do not appear to suffer from this behavior.
Does anyone know why this is happening, or have ideas on how to fix this behavior?
[EDIT] I've found that coming back a half hour later to try again worked, but I'd still like to know why this is happening and how to correct it.