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


Click here to return to the 'Are you sure...' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Are you sure...
Authored by: TrumpetPower! on Feb 25, '05 04:07:48PM

…that it isn't just timing out on a reverse DNS lookup? I can't remember the last time I had this kind of delay when connecting to a service that wasn't caused by a lack of a reverse DNS entry.

As a quick check, run this from Terminal:

for ip in `ifconfig | awk '/inet / { print $2 }'`; do host ${ip}; done

(For the test to be the most meaningful, you'd have to look up the IPs on the server.)

If you experience a similar delay, and especially if you get something that says, "NXDOMAIN," then the solution is to fix DNS. If you have a publicly-routable IP address that's causing the problem, have a chat with your ISP. If you're using private IPs, considering setting up your own local caching DNS server…and make it authoritative for your local IP range.

Cheers,

b&



[ Reply to This | # ]
Are you sure...
Authored by: sbfaulkner on Feb 25, '05 09:51:56PM

100% sure... both client and server names and addresses resolve both forwards and in reverse.

Also, remember, I said that the -I option fixes the problem... therefore, it is RFC931 related.



[ Reply to This | # ]