- A single subnet (such as 192.168.1.0/24)
- A router that provides DHCP, DNS, NAT and firewall services
- Internet access
In this post, we're going to look at some of the aspects of the typical home network and do the planning for the changes required for Unit34.co. Networking knowledge is essential.
Planning your subnets
|Subnet Mask / Prefix Length||/24||/64|
|First Usable Address||192.168.34.1||FD00::34:0:0:0:0|
|Last Usable Address||192.168.34.254||FD00::34:FFFF:FFFF:FFFF:FFFF|
In future, we are planning to expand our Windows domain to multiple Active Directory sites. For these sites, we are going to use the third octet of the Class C private address 192.168.x.0/24 to indicate the subnet.
Assigning IP address to your hosts
|Host Name||IP Address||Description|
|R0||192.168.34.1||Our network router called R0 (Router 0).|
|Carbon||192.168.34.251||A physical server running File and Storage Services and Hyper-V. The one used in this blog is a WD Sentinel DS6100.|
|Hydrogen||192.168.34.254||A virtual machine running on our Hyper-V host Carbon. Hydrogen will be our Active Directory domain controller, DHCP and DNS server.|
DHCP and DNS services will be provided by your router until we set up our first domain controller. We'll continue to use the router to provide Network Address Translation (NAT) and firewall services. At this point we do not need to open any ports or define any rules for these services.