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 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.
Bind handles split-horizon rather well, and you can script swapping
in and out the zone files and restarting if you really need to do
that on the fly.
I'm actually a huge fan of the OS X resolver mechanism, which
basically boils down to:
put a file with the name of the DNS domain in /etc/resolver, with
lines representing the nameservers you want to talk to *for that zone
only*.
Run lookupd -flushcache to flush your resolver cache.
I use this very successfully for changing what server does the
resolving when I am on the VPN as opposed to when I ain't.
Adam
