Lab 02 ‐ Server 2019, ADDS and DNS - Isaiah-River/SYS-255-02-SYSAdmin GitHub Wiki

To start this lab we began by confirming our ping to champlain.edu still works on our workstation VM. image

I then configured the AD01 computer to have an ethernet cable. image

After this I renamed the computer to the naming convention used, in this case ad01-isaiah. image

I then created a new local administrator account using a similar process as Lab 01, and then added it to the ad01-isaiah\Administrators group

image

After this I configured my IPV4 for my ethernet connection. Initially I ran into an issue where I had two ethernets showing up. The reason for this is I had added the ethernet adapter to AD01 without removing the WAN connection. After this I restarted the VM and tested if I had external connectivity by pinging google.com.

image

After confirming I was able to ping google.com, I opened server manager and under "Manage" clicked add roles and features. I went through the installation wizard and selected to add the Active Directory Domain Services under the server roles tab. Towards the end of the installation I choose the restart destination server option and confirmed. After this I confirmed that I did indeed change the hostname of the computer. After I reconfirmed this, I configured the server to be the primary domain controller by clicking the yellow sign, and clicking promote this server to domain controller. When going through the installation, I made sure to change the deployment operation to add a new forest named isaiah.local, and provided a DSRM password that could be used if things went wrong. After a long reboot, I logged into my new AD Administrator account using the credentials ISAIAH\Administrator. When I logged in I confirmed that my DNS for my ethernet had changed to 127.0.0.1, the local loopback adapter for ad01, and that DNS queries that are not being handled locally are being fowarded to my firewall, fw01-isaiah. image

I then tried pinging my firewall by IP and name to show that my DNS is not capable of resolving by name. image

After this I navigated to DNS Manager, and under Forward Lookup Zones clicked "New Host (A or AAAA)." I then named it to my firewall, fw01-isaiah, and set its IP to 10.0.5.2, and checked the "update associated pointer (PTR) record" box. After checking through a warning message, I navigated to the "Reverse Lookup Zone" in DNS Manager, and added a New Zone. After going through the wizard I set the Network ID to 10.0.5, then went back to my newly created forward lookup zones, and unchecked and rechecked the "update associated pointer (PTR) record" box. After this I navigated to Active Directory Users and Computers, and added a new User with the name isaiah.river-adm, and than added the account to the group "Domain Admins." After this I created another account without the administrative privileges with just the credentials of isaiah.river. I then navigated to my wks01-isaiah VM to change the DNS to our newly created AD DNS server so that it is not going directly to the firewall. After this I needed to join the domain on my ws01-isaiah VM. I did this by navigating to my system settings, and changing my domain to "isaiah." After logging in with my isaiah.river-adm credentials, I successfully changed the domain of the wks01 workstation, and restarted the VM. After this I ran some commands in wks01's PowerShell, while logged into my new domain, to showcase that I've completed various parts the lab, and fulfilled the labs deliverables.

image