> Or alternatively make TCPIP DATA point to a local cache-only DNS and
> point that to the proper DNS to resolve (although you normally would
> not need to change that but let it find working DNS itself). I would
> not use the VM TCP/IP DNS anymore for this - running bind on Linux
> might be wiser
On Jul 27, 2007, at 12:13 PM, Rob van der Heij wrote:
On 7/27/07, Alan Altmark <[EMAIL PROTECTED]> wrote:
Sort of. If you keep a copy of TCPIP DATA in SFS accessed ahead
of the
592 disk, you can update it on the fly. YMMV.
Or alternatively make TCPIP DATA point to a local cache-only DNS
On 7/27/07, Alan Altmark <[EMAIL PROTECTED]> wrote:
> Sort of. If you keep a copy of TCPIP DATA in SFS accessed ahead of the
> 592 disk, you can update it on the fly. YMMV.
Or alternatively make TCPIP DATA point to a local cache-only DNS and
point that to the proper DNS to resolve (although yo
On Friday, 07/27/2007 at 10:37 EDT, [EMAIL PROTECTED]
wrote:
> Is there a way in TCPIP, on VM, to dynamically change what DNS ip addr.
VM
> points to?
Sort of. If you keep a copy of TCPIP DATA in SFS accessed ahead of the
592 disk, you can update it on the fly. YMMV.
> I've tried the NETS
Is there a way in TCPIP, on VM, to dynamically change what DNS ip addr. VM
points to?
I've tried the NETSTAT OBEYFILE but it doesn't like the record types in
the TCPIP DATA file.
Thanks
Steve
