Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'A possible fix for slow SSH connections' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A possible fix for slow SSH connections
Authored by: teefour on Apr 02, '05 06:13:03PM

tcpdump showed me that my mac won't try the order of preference which lookupd is supposed to use, it tries mDNS (Rendezvous) instead. Adding an address to /etc/hosts will fix it, but a better way would be to set the search to hosts first, followed by dns and mDNS afterwards.
So far i haven't bothered because the following in ~/.ssh/config

Host myserver
Hostname ip-address
Port 22
User foo

fixed it for me. (the reverse still doesn't work, but it's fast enough this way)

[ Reply to This | # ]
sshd, lookupd, reverse DNS
Authored by: sjk on Apr 03, '05 07:06:49PM
That might explain the "Apr 3 11:48:26 hostname sshd[1731]: reverse mapping checking getaddrinfo for failed - POSSIBLE BREAKIN ATTEMPT!" warnings from sshd even when reverse DNS is properly configured. But I don't see any way to configure lookupd to avoid that; it's currently using:
LookupOrder: Cache FF DNS NI DS
_config_name: Host Configuration
Another symptom is the who command (for instance) displaying the IP address for remote hostnames, while DNS PTR lookups return accurate data.

Anyone know what needs to be tweaked so address-to-name lookups will work properly, without creating static host entries, when DNS is verified as correctly configured?

[ Reply to This | # ]