From: Patrick Townsend <email@example.com> > Leif, > I erred when I said the FTP server does a lookup on its own domain name. > Actually it does a look up on its own IP address to get the domain name. > Maybe it would help if I actually quoted IBM on this issue. Speaking of the > delay: > > "Yes, this comes up occasionally.... and no, there's no way to turn it off. > However, there's an easy workaround: just put the system's name and IP > address in the local host table, and set Host name search priority on > CHGTCPDMN to *LOCAL. (Performance-wise, that's a good thing to do > anyways.) > > The reverse lookup is for the SERVER address, not the client address! It's > used to get the name to put into the initial 220 response. As long as the > server address is in the host table (and it's set to search local first), > the delay shouldn't happen." > > Hope this helps. With everybody's help I think I understand what is going on. Although it is not very intuitive! But who am I to expect it to be straightforward. I solved the problem in a more radical way by specifying *NONE as the DNS address. I can get away with this because of the way I'm using the AS/400. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.