PING does not run on the TCP/IP stack, it runs on the userid that issued the command.
-----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Shimon Lebowitz Sent: December 19, 2006 12:59 To: [email protected] Subject: Re: DNS question Quoting Rob van der Heij <[EMAIL PROTECTED]>: > On 12/19/06, Shimon Lebowitz <[EMAIL PROTECTED]> wrote: > > > What am I forgetting? > > The TCPIP DATA goes on the 592 disk. It's the client code (e.g. PING, > TELNET) that has to talk to the DNS to translate the host name into an > IP address. The stack has no clue about that. <confused> I don't think I understand what you are saying. I put the altered version of TCPIP DATA on TCPIP2's (my test stack userid) so that the stack would see the DNS lines, doesn't PING run in the TCPIP2 user itself? The 191 is accessed ahead of 592, so doesn't TCPIP2 know about the DNS? </confused> > We used to say that it was a good idea to run the cache-only resolver > that comes with VM TCP/IP (i.e. NAMED) to avoid excessive DNS lookups > going outside VM. Some installations also used it to prime the cache > with a set of important host names (in case the outboard DNS was not > available). But the VM DNS implementation has become a bit dated, so > if you can you should probably avoid that route. Hmmmm.... "used to say it was a good idea".... "you should probably avoid that route"? I actually tried to start NAMSERV )or whatever the builtin DNS is called), including putting the two DNS server addresses in FORWARDERS(?), but it didn't help. I am home now, so I might not remember keywords correctly. Thanks for responding, Shimon ._._._*_|_*_*_*_* The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
