Path: utzoo!utstat!helios.physics.utoronto.ca!jarvis.csri.toronto.edu!mailrus!wuarchive!mit-eddie!uw-beaver!milton!hayes!hayes.fai.alaska.edu!wisner From: wisner@hayes.fai.alaska.edu (Bill Wisner) Newsgroups: news.software.nntp Subject: Re: nntpd questions Message-ID: Date: 5 Feb 90 00:32:58 GMT References: <1990Jan31.222330.8870@ucselx.sdsu.edu> Sender: usenet@hayes.fai.alaska.edu Followup-To: news.software.nntp Organization: The Wisner Salvage and Really Wild Stuff Corporation Lines: 21 In-reply-to: tale@cs.rpi.edu's message of 1 Feb 90 00:08:44 GMT tale@cs.rpi.edu (David C Lawrence): >From your example it looks like getpeername() isn't picking up the >name of ucsd.edu; this happens sometimes though someone more >knowledgeable than I about lower level network interaction can explain >why better than I can. Happens to me all the time. I am on the losing end of a 600ms satellite link to Seattle; this places me in an Internet backwater. Now, say I want to FTP to uunet. I connect to uunet and its FTP server tries to figure out my hostname. uunet's nameserver sends a query to alaska's nameserver, but uunet times out before alaska's response arrives. The FTP server then is not able to figure out what site I'm at and it tells me to get lost. But, the response from the alaska nameserver DOES make it to uunet; uunet's nameserver promptly caches that response, and the second time I try everything is peachy. Anybody with slow links to the rest of the Internet is prone to this problem. w.