Tuesday, July 30, 2013

Time-travelling DNS

I’m going to have to rebuild the DNS of my test lab domain.

At some point, it WILL happen.

When it does, what would I like to tell my future self?

IP addresses are irrelevant, because within the test network, those change all the time. (That would be the point of the home lab, wouldn’t it? To be able to build and rebuild as much as I want from within Workstation 9 and the VM’s?)

I think that I would like to remind myself that, when setting up a home lab for the first time, VMnet8 (NAT) is going to be your very bestest friend.


Open the VMware "Virtual Network Editor" to see which IP subnet’s configured and to also disable the “local DHCP service to distribute IP address to VMs”.


Then, inside each VM? Go with IP address ranges
192.168.xx.3...50 (fixed, for the DC’s) and
192.168.xx.51...100 (for the clients & lab boxes).

The gateway address to use for configuring the Ethernet adapters in the VMs is 192.168.xx.2. You can find this by clicking on the “NAT Settings…” button in the Virtual Network Editor window.

NAT Settings_2013-07-25_21-52-21


Then, once all that’s done:
1. set each VM's DNS IPv4 server settings to point to the virtual DC


2. on the DNS servers / DC’s, setup DNS forwarding to send DNS requests for other domains (that is, for the Internet) to the same IP as listed as “DNS Server” on the Host PC.


Last step, as always, is to prove it works. A quick test is this blog. If that succeeds, then check for updates using Windows Update.

No comments:

Post a Comment