[BLU] ssh delays

[jc at trillian.mit.edu (John Chambers)]

Chris Janicki writes:
|
| 2-cents... I've read that nslookup does not use the same networking=20
| libraries/kernel routines/whatever that are used by applications (such a=
| s=20
| SSH).  So there is a possibility that nslookup may work, but yous=20
| application can still fail to reverse lookup. =20
|
| I've seen this happen before, where nslookup works, but my Java app=20
| stalls for 5-min, then continues merrily along.  It's a long shot, but i=
| f=20
| all else fails, try to write a small app to double-check the reverse=20
| lookup.  (I could write a small Java version of nslookup If you'd like.)=


Good idea.  It so happens that I have my own program  that  looks  up
host   names   and   IP  addresses  by  calling  gethostbyname()  and
gethostbyaddr().  I've seen times when  it  disagrees  with  nslookup
about  what is defined.  I tried it on both ends of a link, and again
it resolved all the FQDNs and IP addresses instantly.

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).