Another easy way to resolve the reverse lookup issue is to make /etc/hosts entries for the IPs you ssh from and make sure the "hosts:" line in /etc/nsswitch.conf has "files" listed before "dns". (i.e. "hosts: files dns"). Be careful with the /etc/nsswitch.conf file, as changing other lines incorrectly can cause problems.
This problem is caused by ssh'ing locally from your internal network which is usually private IP addresses (i.e. 192.168.x.x, 10.x.x.x, or 172.16.x.x - 172.31.x.x) and not resolvable via DNS unless you run your own internal DNS server with a reverse IP zone for your local private subnet.
Another recommendation I would make, would be to install Denyhosts if you expose ssh to your internet connection so you can connect via SSH from the Internet. Denyhosts will prevent password attacks of your SSH server from the Internet by denying access to anyone that tires to log in to restricted logins or repeatedly tries to log in with the wrong password. Add your internal IPs to the "allowed-hosts" file to prevent yourself from being locked out. The documentation for Denyhosts will help with this.
Regards
Main Topics
Browse All Topics





by: nabeelmoiduPosted on 2009-09-12 at 12:12:23ID: 25317534
slow initial login could be due to reverse dns issues..In file /etc/ssh/sshd_config: S no
UseDN
slow transfer rates could be due to tcp window sizes...try altering the sysctl parameters