Re: vmware fusion and enclosing dnscache

You can configure which "virtual switch" each virtual Ethernet adapter  
is connected to - it can either share a switch with an external  
physical network adapter (so the VM gets its own external IP address),  
be NATted (so outbound traffic will share an IP address with the host)  
or a "host only" network, which will give your host a virtual Ethernet  
adapter which can talk to the VM's adapter, without any external  
access available.

In this case, you need to give the virtual machine either an external  
IP address (then configure dnscache exactly as you would if you wanted  
it to be a cache for your LAN) or give it both an internal only  
address (so your workstation can query it) and NATted access to the  
host's external address. The latter is more complex to set up, but  
would be necessary in some restrictive scenarios (for example, if your  
host machine is on a company or university network which will only  
give you one IP address).


James.

On 11 Oct 2008, at 23:50, Peter Dambier wrote:

> Under linux I had lo = 127.0.0.1 and could
> ifconfig lo:1 127.0.1.1 ... lo:2 127.0.2.1 and so on.
>
> I am afraid those wont leave the virtual host. Although with
> windows and linux for windows it did.
>
> There was a virtual network device for windows that did
> connect to the ethernet and let you configure a different
> mac address for the linux.
>
> Either you need your own network adapter for the virtual system
> or you need a driver in VMWare to share the adapter.
>
> Kind regards
> Peter
>
>
> Alexy Khrabrov wrote:
>> I wonder if folks configured dnscache and a Mac to serve as a DNS  
>> server
>> for a VMWare Fusion image running on it.  How do you configure the  
>> image
>> (blasted Windowz) and how do you setup the IP for the dnscache --
>> obviously 127.0.0.1 will not do anymore?