On Thu, 29 Mar 2007 20:48:00 +0200, Chris Mason <[EMAIL PROTECTED]> wrote:
A few comments and glosses on Chris's comments. >... "resolver" trace - one of his favourite traces :-) And not a comment about someone having "a favorite trace". Chris could have added "... sick puppy ...". >... first time anyone at "your site"... needs to use the "resolver". But don't forget that TCP/IP always needs the RESOLVER whether or not it needs to do name resolution so some thought needs to go into configuring the parts of TCPDATA that the resolver uses. >... >... ask your partner for his/her IP address to try in place of the >name. That would have got you past any problems translating the name to an IP address. ... But remember that Network Address Translation by be involved so the address know by the partner may not be the address know by you. And the NATing could be done at either end (or both ends) of the connection. Using the IP address is certainly the first thing to try, but it isn't a definitive test. >... >... If this FTP connection is not one that *requires* a name >to be established in name servers in the Internet, you may as well >just use the IP address. I would add "for testing" to Chris's statement. efore doing this in production, check the standards and procedures of your shop. They demand use of names. (Ours certainly does. My last 2 shops have done so.) >...The reason I suggest this is that with an undeveloped "resolver" >environment, building a local name file is a bit of a pain[2] ... Amen! Luckily there are some fairly simple RESOLVER config parms that allow for a common "hosts" definition to be shared between MVS and Unix environments in z/OS. But please see my next comment. >... >If the answer to the question is that you - "your site" - would really >like to have name to IP address mapping in local files as required, >then we could recommend getting current with the way he "resolver" >should be set up these days. But definitely check that this is allowed by your site. At some shops (like mine) that prohibit use of IP addresses you will also find "hosts" files prohibited, and for the same reason. LPAR-based definitions of IP addresses is almost as bad as a jobstream-based definitions of IP addresses - too many places containing addresses that must be changed when addresses change. With an environment full of mergers and aquisitions, changing IP addresses is common. Having those addresses anywhere but corporation-wide name servers may not be allowed. Pat O'Keefe ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
