Nt1330 Lab 2 Answer
2678 words 11 pagesLab 2 Answer Key
Configuring DNS and DHCP
This lab contains the following exercises:
Exercise 2.1 Designing a DNS Namespace
Exercise 2.2 Creating a Zone
Exercise 2.3 Creating Domains
Exercise 2.4 Creating Resource Records
Exercise 2.5 Creating a Scope
Exercise 2.6 Confirming DHCP Server Functionality
Exercise 2.7 Configuring DHCP Reservations
Workstation Reset: Returning to Baseline
Estimated lab time: 100 minutes Exercise 2.1 | Designing a DNS Namespace | Overview | You have been tasked with creating a test DNS namespace structure for your organization. Your first task is to design that namespace by specifying appropriate domain and host names for the computers in the division. | Completion time | 15 minutes |
1. …show more content…
From the context menu, select New Host (A or AAAA). The New Host dialog box appears.
2. In the Name text box, key the host name of the Internet Web server you specified in your namespace design.
3. In the IP Address text box, key 172.17. xx.201, where xx is the number assigned to your computer by your instructor.
4. Click Add Host. A DNS message box appears, stating that the resource record was created.
Question 4 | What must you do before you can select the Create associated pointer (PTR) record checkbox in the New Host dialog box? Answer: Before you can select the Create associated pointer (PTR) record checkbox in the New Host dialog box you must create a Reverse Lookup Zone. |
5. Click OK. A new, blank Add Host dialog box appears.
6. Repeat steps 2 to 4 to create Host records for the Internet FTP and e-mail servers in your namespace design. For each resource record, use a different IP address on the 172.17. xx subnet.
7. In the three domains you created in Exercise 2.3, create Host resource records for all of the remaining computers in your namespace design, using the names you specified in your diagram and a different IP address in the 172.16. xx (start from 172.16.##.9) subnet for each record.
NOTE | For the purposes of this exercise, the actual IP addresses you use when creating your resource records do not matter. In an actual DNS deployment, you must