please read files for instructions
Full Name: Eliezer Andujar Date/Time Started: __________ CSEC-378/418 - Minilab 3 Deliverable and Instructions: This minilab makes use of the Windows Server 1 VM, Windows 10 VM, and Linux Server 1 VM available through the Netlab environment. For instructions on how to get connected to the Netlab environment, please consult the Lab Connectivity Guide on D2L. The submission file for this assignment will be a pdf version of this document, with your answers and screenshots added. Each correctly answered question will count for 1 point. Each screenshot will also count for 1 point and will be evaluated on whether it fully meets the requirements of the screenshot prompt. Your score will be determined by the percentage of total questions and screenshot prompts answered correctly. Answer the questions below the prompts indicated in blue. If a question is multi-part, you must answer all parts correctly to receive the point for that question. No partial credit will be given. Add screenshots below the prompts indicated in blue. When adding screenshots to the document, include any command itself (when applicable), as well as the output or requested information. Ensure that each screenshot is readable in-line in the submission document. If I am unable to read the contents of your screenshot in-line in the document because it is too large, it will not count for credit. Do not include screenshots of your whole desktop or whole application window to when the screenshot prompt is asking about one single part of the output. ** Use this link to access the lab 1. https://netlab.cdm.depaul.edu/home.cgi 2. User: CSEC378_Student23 3. Password: Fossil2021! Minilab 3 – DNS Step 1: Use the Netlab environment to access your Windows 2019 Server 1. Use the drop-down menu next to the server’s name to select “Send CTRL+ALT+DEL” to get a sign in prompt. Sign in with the username Administrator and the password CSEC378418! Step 2: When you sign in you will be prompted with a Server Manager window. If you are not automatically prompted, you can open Server Manager from the Start Menu. Familiarize yourself with the interface, this is your main application for general server administration. More specific tools can be found under the Tools drop down in the top right. Click on the Local Server section on the left pane to view details about the local server. Make note of the Ethernet0 interface IP address. Take a screenshot of this properties pane, including the IPv4 address of your server. Step 3: Install the DNS role on your Windows Server 1. From the upper right corner of Server Manager, select Manage > Add Roles and Features. Step 3a: Under Before you begin, select Next. Step 3b: Under Select installation type, leave the default and select Next. Step 3c: Under Select destination server, leave the default and select Next. Step 3d: Under Select server roles, select DNS Server. You will be prompted to confirm that you want to install additional features that support DNS. Again, leave the defaults, and select Add Features. Then back under Select server roles select Next. Step 3e: Under Select features, leave the defaults and select Next. Step 3f: Under DNS Server select Next. Step 3g: Under Confirm installation selections, select the checkbox at the top to auto restart the server if required. Select Yes on the prompt that asks you to confirm that you want to allow automatic restarts. Step 3h: Take a screenshot of the Confirm installation selections page and include it below. Step 3i: Click Install. Then wait a minute for the installation to complete. Your server may or may not restart during the installation. You will know it is complete when you see the message “Installation succeeded on server1.” Step 4: Return to Server Manager and you should see a new DNS option available on the left side, showing that the DNS role has been installed. This section will show you general alerts and status information about the DNS service. In order to make configuration changes you will need to use the DNS Management Console. Under Tools in the top right corner, choose DNS to open the management console. Step 5: Within the DNS manager you will see your SERVER1 in the left pane. If you click on SERVER1, you will see folders for forward and reverse lookup zones as well as some other options. For first time setup of your DNS server right click on SERVER1 and select the option Configure a DNS server. Step 6: You will be presented with a configuration wizard for setup of your DNS server. From the welcome screen click Next to get started with the DNS server configuration. Step 6a: Under Select configuration action choose the option to Create forward and reverse lookup zones and click Next. Step 6b: Under Forward lookup zone leave the default yes option and click Next. Step 6c: Under Zone Type leave the default primary zone option and click Next. Step 6d: Under Zone Name enter your CampusConnect username followed by “.csec” and click Next. For example, my zone name would be knaught4.csec Step 6e: Under Zone File leave the default file name and click Next. Step 6f: Under Dynamic Update leave the default do not allow and click Next. Step 6g: Under Reverse lookup zone leave the default yes option and click Next. Step 6h: Under Zone Type leave the default primary zone option and click Next. Step 6i: Under Reverse Lookup Zone Name leave the default IPv4 and click Next. Step 6j: On the next prompt, under the Network ID section enter the first three octets of your pod network. These will be the same first three octets of your Windows Server 1 IP address that you identified after Step 2, you will see the corresponding in-addr.arpa address under Reverse lookup zone name. When done, click Next. Step 6k: Under Zone File leave the default file name and click Next. Step 6l: Under Dynamic Update leave the default do not allow and click Next. Step 6m: Under Forwarders leave the default no option and click Next. Step 6n: You will be prompted to finish your setup, close the wizard by clicking Finish. Note: From here on out I will refer to your forward lookup zone as yourname.csec and your reverse lookup zone as X.10.10.in-addr.arpa, since these will be different for every student. Additionally, any time you see a reference to 10.10.X.100 or other similar IP address, I expect you to substitute the X for your pod network’s third octet. Substitute these in commands and configuration prompts accordingly. Step 7: Return to the DNS management console. In the left pane click the drop down next to SERVER1 to show the available options. Also click the drop downs next to the Forward Lookup Zone and Reverse Lookup Zone to show your newly created zones. Take a screenshot of the left pane showing your server’s name and your forward and reverse lookup zone names and include it below. Step 8: Double click on your forward and reverse lookup zones. You will see two records that were created by default in each location, one is an SOA and one is an NS record. Take a look at these records, you can double click them and look through the available configuration tabs at the top of the window. Do some research on the purpose of each of these records. Question 1: What is the purpose of an SOA record, what does it define? Question 2: What is the purpose of an NS record, what does it define? Step 9: Edit the NS records for your forward and reverse lookup zones. Double click on the NS record and go to the Name Servers configuration tab. Under the list of name servers you will see server1. with an unknown IP address. Update each record to have server1.yourname.csec. as the FQDN and an IP address of 10.10.X.100. Click Apply when done. Make sure to update the NS record in both your forward and reverse lookup zones. Step 10: Right click on yourname.csec forward lookup zone and select the option to add a New Host (A or AAAA). Under the Name section enter server1 and under the IP address section enter the IP of your Windows Server1. Click the check box to create associated PTR record and then click Add Host. Step 11: Use the Netlab interface to access your Linux Server 1. You can login with the username student and the password student. When you are logged in use dig to query your new nameserver. Run the following command: dig @10.10.X.100 ns yourname.csec Question 3: Explain the components of the dig command above, what does each section of the command mean? Take a screenshot of the command you ran and the dig output and include it below. Question 4: You will notice that the response contains an Answer section, but also an Additional section. What information is included in the Additional section? Why does the DNS server include this additional information as part of the response? Step 12: In the answer section of your dig output, you should see an NS record containing the name of your server 1. Now use dig to issue another query, this time for an A record for server1.yourname.csec instead of an NS record for yourname.csec. Question 5: What command did you use to issue this query? Take a screenshot of the answer section of the response you received and include it below. Step 13: Issue another query, but this time request the A record for server2.yourname.csec instead of server1. You will get a response from the DNS server but it will not contain an answer. Question 6: Why doesn’t the DNS response contain an answer? Step 14: Use dig to perform a reverse lookup on the IP address of your server 1. Use the following command to perform this query: dig @10.10.X.100 -x 10.10.X.100 Question 7: What is the purpose of the -x flag in this dig command? Take a screenshot of the answer section of the response you received and include it below. Step 15: Return to your Windows Server 1. Repeat the process from Step 10 to create new A and PTR records for the following names and IP addresses: Name IP Address server2 10.10.X.101 win10 10.10.X.110 linux1 10.10.X.120 linux2 10.10.X.130 Step 16: By clicking that checkbox to create associated PTR record for each A record, you created two entries for each host – one reverse lookup record (PTR) and one forward lookup record (A). You should see entries for