On Mon, 26 Apr 2010 14:41:33 PDT, Robin Axelsson <gu99r...@student.chalmers.se> wrote: >> the workaround doesn't have to be to have a reverse mapping for >> the client IP address but to set it up so that you get an immediate >> response from the system that there is not such reverse, without a >> delay. > > > And I presume that this is what is done when adding the IP-address and > name in the /etc/inet/hosts and /etc/inet/ipnodes files (I assume that the > entries "ipnodes: files dns" and "hosts: files dns" are present in > /etc/nsswitch.conf file). However, this is not optimal over a local network > using DHCP negotiation. > > So, the other way you suggested would be to get rid of the timeout. I > found out that nslookup is actually a wrapper for dig and that the > configuration for name resolution could be found in the /etc/resolve.conf. > So I guess at least 5 seconds would be reasonable to wait for the DNS to > respond so my bet is that the line: > > options timeout:5 > > would get rid of the excess time spent on waiting during the reverse > lookup being done during ssh negotiation. > > Thanks again for your responses! It feels good to know that this is > actually an issue that is being worked on and not just a "noob" issue.
The delay indicates a problem with your network's DNS configuration; 5 seconds much exceeds the typical range in milliseconds for a response. As I mentioned, name-service-cache (nscd) will help after the initial lookup (if successful), but the delay is abnormal. -Albert _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
