Duncansapien’s Techblog

Overview

The plan is to create a complete test environment for Active Directory inside VMware Workstation 6.5. To replicate as closely as possible a real-world scenario, existing Linux-based DNS servers will be used. When AD is installed, the first Windows Server will also act as a DNS server but only for AD - forwarding queries to the existing Linux servers for all non-AD queries.

The environment we want to construct is as follows:

Network

• VMNet1 - Private network shared with host, network 192.168.19.0 used for 99% of work
• VMNet8 - NAT, used infrequently to obtain Microsoft updates and software packages (BIND) from internet then disconnected, network 192.168.85.0.

DNS

• 2 x Suse 10.3 DNS guest servers (primary, secondary)
  dns1.mydept.myorg, 192.168.19.201
  dns2.mydept.myorg, 192.168.19.202
  

Windows Servers (to host AD, network shares, etc)

• 2 x Windows Server 2003 Standard guests
  w2k03-a.mydept.myorg, 192.168.19.5
  w2k03-b.mydept.myorg, 192.168.19.6
  

XP hosts (to login to AD)

• 2 x XP SP3 guests
  xp-a.mydept.myorg, 192.168.19.10
  xp-b.mydept.myorg, 192.168.19.11
  

Why Suse 10.3, you might wonder? Simply because from a previous exercise I have a dual-booting XP and OpenSuse 10.3 VM available, sharing a small (8Gb) virtual hard disk and this seems ideal.

Figure 1: The Active Directory Test Environment

First Steps: The DNS Servers

We wish to establish a Suse 10.3 VM with the BIND DNS package, re-using a VM from earlier work (see “Dual-booting XP with Suse 10.3“).

The following references will be used: Quick HOWTO: Configuring DNS

We want to rename the Suse machine and see which services are in use, along the way installing the nanoemacs editor for convenience.

Boot the Suse10.3 VM and open a command shell

Article being written, but aren’t these colours nice?