1. ADDS with Routing Services
Pratul
Configuration
ENTERPRISE - BUNGIE DNS - 10.192.1.1
(10.192.0.0/16)
ROOT DOMAIN - bungie.com (10.192.1.0/24)
| Bungie - DC | Private IP - 10.192.1.1 / Subnet Mask - 255.0.0.0 / GW Network - 10.192.1.12 |
| Bungie - ADC | Private IP - 10.192.1.4 / Subnet Mask - 255.0.0.0 / GW Network - 10.192.1.12 |
| Bungie - Router | Private IP - 10.192.1.12, 192.168.1.12, 172.2.169.82 (NAT) / Subnet Mask - 255.0.0.0, 255.255.255.0, 255.255.0.0 (NAT) |
| Bungie - PC1 |
CHILD DOMAIN - 343i.bungie.com (10.192.2.0/24)
| 343i - DC | Private IP - 10.192.2.1 / Subnet Mask - 255.0.0.0 / GW Network - 10.192.1.12 |
| 343i - ADC | Private IP - 10.192.2.4 / Subnet Mask - 255.0.0.0 / GW Network - 10.192.1.12 |
| 343i - PC2 (Using WDS) |
ENTERPRISE - RAVEN DNS - 192.168.1.1
(192.168.0.0/16)
ROOT DOMAIN - raven.com (192.168.1.0/24)
| Raven - DC | Private IP - 192.168.1.1 / Subnet Mask - 255.255.255.0 / GW Network - 192.168.1.12 |
| Raven - ADC | Private IP - 192.168.1.4 / Subnet Mask - 255.255.255.0 / GW Network - 192.168.1.12 |
| Raven - PC3 (Using WDS) |
CHILD DOMAIN - activation.raven.com (192.168.2.0/24)
| Activation - DC | Private IP - 192.168.2.1 / Subnet Mask - 255.255.255.0 / GW Network - 192.168.1.12 |
| Activation - ADC | Private IP - 192.168.2.1 / Subnet Mask - 255.255.255.0 / GW Network - 192.168.1.12 |
| Activation - PC4 (Using WDS) |
AIM
The purpose of this lab is not only to implement Active Directory concepts but also getting acquainted with its fundamentals as well.
My First Requirement is simulating the environment of two Enterprise Forests. Each Forest have their respective Root Domain Controllers of respective Domains along with Additional Domain Controllers. Each Domain-Joined PCs to every domain present within Forest for applying roles & features.
Once setup, I will then be setting up above IPs as mentioned in “Configuration “.
My second requirement, I will then be setting up Forest/External Trust between two respective Forests. This can be achieved with the help of a router.
For this I relied on an AD Role - Remote & Routing Access in bungie-router server. I have setup below services.
LAN Routing
NAT Routing
Configured Server Machines using these flavors of Windows Server:
Windows Server 2016
Windows Server 2019
Windows Server 2022
Therefore, I started building Windows Servers using HOSTED OS (Type-2) Hypervisors such as Hyper-V.
Subscribe to my newsletter
Read articles from Pratul directly inside your inbox. Subscribe to the newsletter, and don't miss out.
Written by
Pratul
Pratul
A passionate L1 Server Engineer with a growing focus on DevOps practices. With experience in server administration, troubleshooting and infrastructure management, I am skilled at optimizing workflows through automation and CI/CD pipelines. Currently working with cloud platforms like AWS & Azure, virtualization technologies, and configuration management tools. Committed to enhancing efficiency and productivity. Through this blog, I will be sharing hands-on insights, tutorials, and practical tips aimed at helping fellow professionals in server engineering and DevOps.