wisner@hayes.fai.alaska.edu (Bill Wisner) (02/05/90)
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. <wisner@hayes.fai.alaska.edu> <wisner@mica.berkeley.edu>
mdb@ESD.3Com.COM (Mark D. Baushke) (02/05/90)
On 5 Feb 90 00:32:58 GMT, wisner@hayes.fai.alaska.edu (Bill Wisner) said: Bill> tale@cs.rpi.edu (David C Lawrence): David> From your example it looks like getpeername() isn't picking up David> the name of ucsd.edu; this happens sometimes though someone David> more knowledgeable than I about lower level network interaction David> can explain why better than I can. Bill> Happens to me all the time. I am on the losing end of a 600ms Bill> satellite link to Seattle; this places me in an Internet backwater. Bill> Now, say I want to FTP to uunet. I connect to uunet and its FTP server Bill> tries to figure out my hostname. uunet's nameserver sends a query to Bill> alaska's nameserver, but uunet times out before alaska's response Bill> arrives. The FTP server then is not able to figure out what site I'm Bill> at and it tells me to get lost. But, the response from the alaska Bill> nameserver DOES make it to uunet; uunet's nameserver promptly caches Bill> that response, and the second time I try everything is peachy. Bill> Anybody with slow links to the rest of the Internet is prone to this Bill> problem. Bill> w. <wisner@hayes.fai.alaska.edu> <wisner@mica.berkeley.edu> Sounds to me like you should get a secondary nameserver which is 'closer' to the NFSNet backbone. Redundancy of DNS information makes life much simpler. At the least, try finding a secondary site on the East Coast or in the South somewhere at the 'other end' of the Internet from you to avoid worst case delay for name lookup. -- Mark D. Baushke mdb@ESD.3Com.COM
mdb@ESD.3Com.COM (Mark D. Baushke) (02/05/90)
On 5 Feb 90 02:37:56 GMT, mdb@ESD.3Com.COM (Mark D. Baushke) said: Mark> Sounds to me like you should get a secondary nameserver which is Mark> 'closer' to the NFSNet backbone. Of course, I meant to say an 'additional secondary nameserver'. -- Mark D. Baushke mdb@ESD.3Com.COM
wisner@hayes.fai.alaska.edu (Bill Wisner) (02/06/90)
Mark D. Baushke: >Sounds to me like you should get a secondary nameserver which is >'closer' to the NFSNet backbone. Don't think I haven't tried. Unfortunately, it seems that the person here that's "responsible" for the nameservers is more interested in maintaining a locally written VMS mailer that's actually a relic from an old Honeywell system than taking a few moments to adjust his NS lists. Bureaucracy blows. Bill Wisner <wisner@hayes.fai.alaska.edu> Gryphon Gang Fairbanks AK 99775 "Early one June morning in 1872 I murdered my father--an act which made a deep impression on me at the time." -- Ambrose Bierce
wisner@hayes.fai.alaska.edu (Bill Wisner) (02/06/90)
Mark D. Baushke:
>Of course, I meant to say an 'additional secondary nameserver'.
You were right the first time -- our secondary nameserver is listed as
NSGENG.NWNET.NET -- a machine which no longer even exists! (OK, enough
public bitching on the topic -- unless someone really wants me to
continue..)
Bill Wisner <wisner@hayes.fai.alaska.edu> Gryphon Gang Fairbanks AK 99775