INF204x Module 1 Lab 1: Configuring and Troubleshooting Networking Part 1

Transcription

1 INF204x Module 1 Lab 1: Configuring and Troubleshooting Networking Part 1 Estimated Time: 90 minutes Your organization plans to implement IPv6 in their existing Active Directory environment including Windows 10 computers. In preparation for this implementation, you need to evaluate the scenario that involves IPv6 based communication between a Windows 10 domain member computer and a Windows Server 2012 R2 Active Directory domain controller. Objectives After completing this lab, students will be able to: Configure IPv6 addresses on a Windows 10 computer Configure DHCPv6 on a Windows 10 computer Configure DNSv6 on a Windows 10 computer Configure IPv6 routing on a Windows 10 computer Troubleshoot IPv6 configuration on a Windows 10 client computer Lab Environment The lab consists of two virtual machines: LON-WIN10 - Windows 10 Enterprise client (Adatum.com Active Directory domain member) with IPv4 address of LON-DC1 Windows Server 2012 R2 Datacenter server (Adatum.com Active Directory domain controller) with IPv4 address of Note: It is important to point out that dynamic IPv6 configuration in Windows operating systems typically relies on the combination of two complementing mechanisms. The first of them consists of router advertisements from an IPv6-capable router. The second one is an IPv6 address assignment (along with DNSv6 settings such as IPv6 addresses of DNS servers and DNS suffixes to be assigned to the DHCPv6 client) from a DHCPv6 server. However, this lab currently provides the ability to implement only the second of these two mechanisms, by relying on a Windows Server 2012 R2-based DHCP Server. While this still allows you to implement a functional IPv6 scenario, it requires additional steps that would not be necessary if an IPv6-capable router was present. These additional steps include IPv6 routing table changes (and, in a multi-subnet environment, would also involve assigning a default gateway). Even though it is unlikely that you will have to resort to performing these steps in real-life deployments, we hope that these additional steps will expand your knowledge of IPv6 and potentially might come handy someday while troubleshooting or setting up your own IPv6 lab.

2 Exercise 1: Identify the default network configuration of the virtual machines in the lab In this exercise, you will evaluate the default networking configuration of the lab virtual machines (VMs). The main tasks for this exercise are as follows: 1. Identify IPv4 and IPv6 configuration of the Windows Server 2012 R2 server virtual machine 2. Identify IPv4 and IPv6 configuration of the Windows 10 virtual machine 3. Test IPv4 and IPv6 connectivity between the virtual machines 4. Test DNSv4 and DNSv6 name resolution between the virtual machines Task 1: Identify IPv4 and IPv6 configuration of the Windows Server 2012 R2 server virtual machine 1. Sign in to the Windows Server 2012 R2 (LON-DC1) lab virtual machine with the following credentials: USERNAME: ADATUM\Administrator PASSWORD: Pa$$w0rd 2. On the lab virtual machine, launch Windows PowerShell by clicking on its icon in the taskbar. 3. In the Administrator: Windows PowerShell window, type the following and press the Enter key. Get-NetIPAddress Sort InterfaceIndex FT InterfaceIndex, InterfaceAlias, AddressFamily, IPAddress, PrefixLength Autosize 4. Examine the output and note that the Ethernet interface has both an IPv4 and IPv6 address assigned to it. The IPv6 address starts with fe80:: and has the prefix length of 64. This is a linklocal address. Note that this address contains a suffix (following the % sign) matching the network interface index. Also note that the IPv6 information is displayed first. Again IPv6 is the default and the preferred protocol. Note: Link-local addresses are functionally equivalent to IPv4 APIPA addresses since they facilitate communication within the local subnet. To find out more about link-local addresses, refer to IPv6 for the Windows Administrator: IPv6 Fundamentals at fundamentals/ 5. At the Windows PowerShell prompt, type the following and press the Enter key wf.msc 6. In the Windows Firewall with Advanced Security window, click Inbound Rules in the left window pane. In the list of Inbound Rules in the middle pane, verify that the File and Printer Sharing (Echo Request ICMPv4-In) and File and Printer Sharing (Echo Request ICMPv6-In) rules are enabled for All profiles. Note: With the firewall rules allowing inbound ICMP traffic, we will be able to test connectivity from a Windows 10 domain member lab virtual machine to the Windows Server 2012 R2 domain controller lab virtual machine. We will rely on this ability throughout the remainder of the lab.

3 Task 2: Identify IPv4 and IPv6 configuration of the Windows 10 virtual machine 1. Sign in to the Windows 10 (LON-WIN10) lab virtual machine with the following credentials: USERNAME: ADATUM\Administrator PASSWORD: Pa$$w0rd 2. On your lab virtual machine, click the Windows logo in the lower left corner. Click All apps in the Start menu. In the All apps menu, click the Windows PowerShell folder. In the list of programs in the PowerShell folder, right click Windows PowerShell. In the right-click menu, click Run as administrator. 3. In the Administrator: Windows PowerShell window, type the following and press the Enter key. Get-NetIPAddress Sort-Object InterfaceIndex Format-Table InterfaceIndex, InterfaceAlias, AddressFamily, IPAddress, PrefixLength Autosize 4. Examine the output and note that the Ethernet interface has both an IPv4 and IPv6 address assigned to it. The IPv6 address starts with fe80:: and has the prefix length of 64. This is a linklocal address. Note that this address contains the suffix (following the % sign) matching the network interface index. 5. At the Windows PowerShell prompt, type the following and press the Enter key wf.msc 6. In the Windows Firewall with Advanced Security window, click Inbound Rules in the left window pane. In the list of Inbound Rules in the middle pane, verify that the File and Printer Sharing (Echo Request ICMPv4-In) and File and Printer Sharing (Echo Request ICMPv6-In) rules are enabled for All profiles. Note: Here as well, with the firewall rules allowing inbound ICMP traffic, we will be able to test connectivity from the Windows Server 2012 R2 domain controller lab virtual machine to the Windows 10 domain member lab virtual machine. Task 3: Test IPv4 and IPv6 connectivity between the virtual machines 1. From the Windows 10 (LON-WIN10) virtual machine, switch to the Administrator: Windows PowerShell window, type the command and press the Enter key: Invoke-Command -ComputerName 'LON-DC1' -ScriptBlock {Get-NetIPAddress Where- Object InterfaceAlias -eq 'Ethernet' Select-Object IPAddress} 2. The output should include the listing of the IPv4 and IPv6 address assigned to the Ethernet network interface on LON-DC1. 3. At the Windows PowerShell prompt, type the following command and press the Enter key (make sure to replace the <IPv4 address of LON-DC1> with the actual IPv4 address of LON- DC1 included in the output returned by the command executed in step 1 of this task).

4 Test-NetConnection ComputerName <IPv4 address of LON-DC1> 4. The command tests IPv4 network connectivity between LON-WIN10 and LON-DC1. Verify that the value of the PingSucceeded property in the output returned by this command is True. 5. At the Windows PowerShell prompt, type the following command and press the Enter key (make sure to replace the <IPv6 address of LON-DC1> with the actual IPv6 address of LON- DC1 included in the output returned by the command executed in step 1 of this task). Important: Make sure to remove the trailing % and the interface index from the IPv6 address returned by the command executed in step 1 of this task when using it in the Test-NetConnection cmdlet. Test-NetConnection ComputerName <IPv6 address of LON-DC1> 6. The command tests IPv6 network connectivity between LON-WIN10 and LON-DC1. Verify that the value of the PingSucceeded property in the output returned by this command is True. Note: This confirms that, by default, we can communicate by using IPv6 link-local addresses between two computers on the same subnet (as mentioned earlier, this is a subject to operating system-level firewall rules). Task 4: Test DNSv4 and DNSv6 name resolution between the virtual machines 1. On the Windows 10 (LON-WIN10) virtual machine, from the Administrator: Windows PowerShell window, type the following command and press the Enter key: Resolve-DnsName Name LON-WIN10.adatum.com -DnsOnly 2. The output lists the DNS records associated with the LON-WIN10.adatum.com name. Note that, at this point, there is only an A record (referencing the IPv4 address of LON-WIN10) but there is no AAAA record (which would resolve the LON-WIN10 name to its corresponding IPv6 address). 3. Rerun the same command for LON-DC1 by typing the following command and pressing the Enter key: Resolve-DnsName Name LON-DC1.adatum.com -DnsOnly 4. The output lists the DNS records associated with the LON-DC1.adatum.com name. Note that, in this case as well, at this point, there is only an A record (referencing the IPv4 address of LON- DC1) but there is no AAAA record (which would resolve the LON-DC1 name to its corresponding IPv6 address). 5. You can also verify this running the following command: Test-NetConnection -ComputerName LON-DC1.adatum.com InformationLevel Detailed 6. The output returned by the command will include the AllNameResolutionResults property, which value should contain only the IPv4 address of LON-DC1.adatum.com, since DNS name resolution to its IPv6 address is currently not possible (due to the lack of the corresponding AAAA DNS record).

5 Note: If you rerun the Test-NetConnection cmdlet but specify the hostname of LON-DC1 (rather than its fully qualified domain name), you will actually see both IPv4 and IPv6 addresses returned as the value of the AllNameResolutionResults property. In this case, the cmdlet relies on Link-Local Multicast Name Resolution (LLMNR) mechanism to resolve the name of another host on the same subnet to its link-local IPv6 address. Keep in mind that LLMNR is dependent on the Network Discovery being enabled on the target system (in this case, LON-DC1). Results: After completing this exercise, you will have identified IP configuration of both lab virtual machines (LON-WIN10 and LON-DC1). You also tested IPv4 and IPv6 connectivity as well as DNSv4 and DNSv6 name resolution between them. Exercise 2: Implement DHCPv6. In this exercise, you will implement DHCPv6 to assign IPv6 addresses to Windows 10 computers by using the Windows Server 2012 R2-based DHCP server role. The main tasks for this exercise are as follows: 1. Install and configure DHCP Server role on the Windows Server 2012 R2 lab virtual machine (LON-DC1) 2. Implement DHCP server connection bindings on the Windows Server 2012 R2 lab virtual machine (LON-DC1) 3. Examine the resulting DHPCv6 configuration on the Windows 2012 R2 lab virtual machine (LON-DC11) 4. Examine the resulting DHPCv6 configuration on the Windows 10 lab virtual machine (LON-WIN10) 5. Test IPv6 connectivity between the lab virtual machines (LON-DC1 and LON-WIN10) 6. Modify IPv6 routing table on the Windows 10 virtual machine (LON-WIN10) Task 1: Configure DHCP Server role on the Windows Server 2012 R2 lab virtual machine (LON-DC1) 1. On the Windows Server 2012 R2 lab virtual machine (LON-DC1), in the Server Manager window, click Tools. In the drop-down menu, click DHCP. This will launch the DHCP console. 2. In the DHCP console, right click on the lon-dc1.adatum.com icon and verify that the server has been authorized. If not, click Authorize in the right-click menu. 3. In the DHCP console, right-click the IPv6 node and click New Scope in the right-click menu. This will launch New Scope Wizard. 4. On the Welcome to the New Scope Wizard page, click Next. 5. On the Scope Name page, type in Adatumv6 in the Name textbox and click Next. Note: The naming convention is arbitrary, but you should consider choosing one that will help you identify the purpose of each scope. Our choice is based purely on the fact that there is an existing IPv4 scope named Adatum. 6. On the Scope Prefix page, type in fd44:ecc6:e322:: in the Prefix textbox and click Next.

6 Note: In this lab, we are creating a range that will be allocating Unique Local IPv6 addresses. To find out more about unique local addresses, refer to IPv6 for the Windows Administrator: IPv6 Fundamentals at fundamentals/ 7. On the Add Exclusions page, click Next. 8. On the Scope Lease page, leave the defaults in place and click Next. 9. On the Completing the New Scope Wizard page, ensure that the Activate Scope Now option is set to Yes and click Finish. Important: While at this point the IPv6 scope has been created in activated, the DHCP server is not able to lease IPv6 addresses to DHCPv6 clients because it does not have appropriately configured bindings. To remediate this, you must first assign a static IPv6 address to the network interface reachable by DHCPv6 clients. You should also create an exclusion in the DHCPv6 scope that contains that IPV6 address. You will implement these steps in the next task. Task 2: Implement DHCP server connection bindings on the Windows Server 2012 R2 lab virtual machine (LON-DC1) 1. On the Windows Server 2012 R2 lab virtual machine (LON-DC1), switch to the Start screen, type ncpa.cpl, and press the Enter key. This will open the Network Connections window. 2. Right-click the Ethernet connection and select Properties from its right-click menu. 3. In the Ethernet Properties dialog box, select Internet Protocol Version 6 (TCP/IPv6) and click Properties. 4. In the Internet Protocol Version 6 (TCP/IPv6) Properties dialog box, select Use the following IPv6 address option button. In the IPv6 address textbox, type in fd44:ecc6:e322::dc1. Note that your choice of IPv6 address is arbitrary, as long as the 64-bit prefix matches the one designated for the DHCPv6 scope (we decided to use dc1 as the Interface ID portion of the address purely for convenience). Ensure that the Subnet prefix lenght is set to Click OK. Ignore the message stating that The DNS server list is empty. The local IP address will be configured as the primary DNS server address because Microsoft DNS is installed on this machine. Click OK to close the message box. 6. In the Ethernet Properties dialog box, click Close. 7. Switch back to the DHCP console. Under the IPv6 node, right-click Exclusions and select New Exclusion Range from the right-click menu. 8. In the Add Exclusion dialog box, type in dc1 in the Start IPv6 Address textbox and in the End IPv6 Address textbox. Note: Keep in mind that dc1 in this case has nothing to do with the server name. Instead, this represents the interface ID portion of the static IP address you assigned to the server LON-DC1 (which we simply chose to set to the hexadecimal value dc1). 9. Click Add and click Close.

7 Task 3: Examine the resulting DHPCv6 configuration on the Windows Server 2012 R2 lab virtual machine (LON-DC1) 1. Switch to the Administrator: Windows PowerShell window and, at the prompt, type the following and press the Enter key: Ipconifg /renew6 Ethernet 2. Verify that the output displayed once the command above completes includes the IPv6 address from the DHCPv6 scope you defined earlier. Note: At this point, there are three IPv6 addresses assigned to the Ethernet interface on LON-DC1. The first one is the automatically allocated link-local one (starting with fe80::), the second one is the static one you assigned earlier in this exercise (fd44:ecc6:e322::dc1), and the third one (also starting with fd44:ecc6:e322::) has been provided dynamically by the DHCP server from its DHCPv6 scope. Task 4: Examine the resulting DHPCv6 configuration on the Windows 10 lab virtual machine (LON-WIN10) 1. Switch to the Windows 10 (LON-WIN10) virtual machine. On LON-WIN10, in the Administrator: Windows PowerShell window, type the following command and press the Enter key: Ipconifg /renew6 Ethernet 2. Verify that the output displayed once the command above completes includes the IPv6 address from the DHCPv6 scope you defined earlier. Note: At this point, there are two IPv6 addresses assigned to the Ethernet interface on LON-WIN10. The first one is the automatically allocated link-local one (starting with fe80::) and the second one (starting with fd44:ecc6:e322::) has been provided dynamically by the DHCP server from its DHCPv6 scope. Task 5: Test IPv6 connectivity between the lab virtual machines (LON-DC1 and LON-WIN10) 1. On the Windows 10 (LON-WIN10) virtual machine, switch to the Administrator: Windows PowerShell window, type the command and press the Enter key: Invoke-Command -ComputerName 'LON-DC1' -ScriptBlock {Get-NetIPAddress Where- Object InterfaceAlias -eq 'Ethernet' Select-Object IPAddress} 2. The output should include the listing of all IPv6 addresses assigned to the Ethernet network interface on LON-DC1. At the Windows PowerShell prompt, type the following command and press the Enter key (make sure to replace the <IPv6 address of LON-DC1> with the actual DHCPv6 assigned IPv6 address of LON-DC1 included in the output returned by the command executed in step 1 of this task.

8 Test-NetConnection ComputerName <IPv6 address of LON-DC1> 3. The command tests IPv6 network connectivity between LON-WIN10 and LON-DC1. Notice that the test fails. Important: You might be surprised that the test fails at this point, even though both LON-WIN10 and LON-DC1 appear to have DHCPv6 assigned IPv6 addresses from the same scope and both reside on the same subnet. As we mentioned at the beginning of this guide, this is due to the fact that our lab environment does not include an IPv6-capable router. To remediate this shortcoming, you will need to make IPv6 routing table changes. The steps to accomplish this are outlined in the next task. Task 6: Modify IPv6 routing table on the Windows 10 virtual machine (LON- WIN10) 1. On the Windows 10 (LON-WIN10) virtual machine, from the Administrator: Windows PowerShell window, type the command and press the Enter key: Get-NetRoute InterfaceAlias Ethernet 2. The output should include the listing of the local routing table entries for the Ethernet network interface. Note that the table does not include an entry representing the local IPv6 subnet (fd44:ecc6:e322::/64). This is causing the failure of communication by using the IPv6 address dynamically assigned to LON-WIN10 by DHCPv6. 3. To resolve this, at the Windows PowerShell prompt, type the following command and press the Enter key: New-NetRoute InterfaceAlias Ethernet DestinationPrefix fd44:ecc6:e322::/64 NextHop :: AddressFamily IPv6 RouteMetric The command will return the new route table entries. Note that since we have not included the PolicyStore parameter, the route is added automatically to both ActiveStore and PersistentStore. Effectively, the change takes effect immediately and persists following reboots. 5. At the Windows PowerShell prompt, rerun the following command and press the Enter key (make sure to replace the <IPv6 address of LON-DC1> with the actual DHCPv6 assigned IPv6 address of LON-DC1 included in the output returned by the command executed in step 1 of the previous task). Test-NetConnection ComputerName <IPv6 address of LON-DC1> 6. Note that this time the command succeeded, as indicated by the value True of the PingSucceeded property in the returned output. Important: Note that we did not have to modify the routing table on LON-DC1. The reason for it is that we assigned to it a static IPv6 address in the fd44:ecc6:e322::/64 subnet, which automatically took care of adjusting appropriately its local routing table. You can easily verify this by running the Get- NetRoute InterfaceAlias Ethernet command from the Windows PowerShell prompt on LON-DC1.

9 Results: After completing this exercise, you will have installed and configured DHCP server role on the Windows Server 2012 R2 lab virtual machine, implemented its DHCP server connection bindings, and examined the resulting DHCPv6 configuration on the Windows Server 2012 R2 and Windows 10 lab virtual machines. You also identified an issue when testing IPv6 connectivity between the two lab virtual machines and resolved it by modifying the IPv6 routing table on the Windows 10 lab virtual machine. Exercise 3: Implement DNSv6 In this exercise, you will configure DNSv6 to facilitate reverse DNS lookups from Windows 10 computers by using the Windows Server 2012 R2-based DNS server role. The main tasks for this exercise are as follows: 1. Test DNSv6 name resolution from the Windows 10 lab virtual machine 2. Modify DNSv6 DNS Server settings on the Windows Server 2012 R2 lab virtual machine 3. Configure DHCPv6 scope options on the Windows Server 2012 R2 lab virtual machine Task 1: Test DNSv6 name resolution on the Windows 10 lab virtual machine 1. On the Windows 10 (LON-WIN10) virtual machine, from the Administrator: Windows PowerShell window, type the following command and press the Enter key: Resolve-DnsName Name LON-WIN10.adatum.com -DnsOnly 2. The output lists the DNS records associated with the LON-WIN10.adatum.com name. Note that, at this point, there is not only the A record (referencing the IPv4 address of LON-WIN10) but also the AAAA record (which would resolve the LON-WIN10 name to its corresponding IPv6 address). Important: This might be again a bit of a surprise since you have not configured DNSv6 settings on the Ethernet network interface of LON-WIN10, however, the DHCPv6 client is capable of registering the DNSv6 names by relying on DHCPv6 server. These settings can be managed from the DHCP console, by right-clicking on the IPv6 node, selecting Properties from the right-click menu, clicking DNS tab in the IPv6 Properties dialog box, and modifying the state of the Enable DNS dynamic updates according to the settings below checkbox (along with the two options Dynamically update DNS AAAA and PTR records only if requested by the DHCP clients and Always dynamically update DNS AAAA and PTR records). 3. Now try performing a reverse lookup which should resolve an IPv6 address to the corresponding DNS name. In this case, you will attempt to resolve the IPv6 address which was assigned dynamically to LON-DC1 by using DHCPv6. To accomplish this, type the following command at the Windows PowerShell prompt and press the Enter key (make sure to replace the <IPv6 address of LON-DC1> with the actual DHCPv6 assigned IPv6 address of LON-DC1, which you identified in the previous exercise): Resolve-DnsName Type PTR -Name <IPv6 address of LON-DC1> -DnsOnly 4. You will receive an error message stating that the DNS record does not exist.

10 Note: In order to perform reverse lookups, which rely on the presence of PTR records, you must first create a reverse lookup zone and ensure that it is populated with these PTR records. You will implement these steps in the next task of this exercise. Task 2: Modify DNSv6 DNS Server settings on the Windows Server 2012 R2 lab virtual machine. 1. On the Windows Server 2012 R2 lab virtual machine (LON-DC1), in the Server Manager window, click Tools. In the drop-down menu, click DNS. This will launch the DNS Manager console. 2. In the DNS Manager console, right click on the Reverse Lookup Zones folder and click New Zone in the right-click menu. This will launch New Zone Wizard. 3. On the Welcome to the New Zone Wizard page, click Next. 4. On the Zone Type page, accept the default settings and click Next. 5. On the Active Directory Zone Replication Scope page, accept the default settings and click Next. 6. On the Reverse Lookup Zone Name page, select the IPv6 Reverse Lookup Zone option and click Next. 7. On the Reverse Lookup Zone Name page, in the IPv6 Address Prefix text box, type in fd44:ecc6:e322::/64 and click Next. 8. On the Dynamic Update page, select the Allow both nonsecure and secure dynamic updates option and click Next. 9. On the Completing the New Zone Wizard page, click Finish. This will result in creation of the reverse lookup zone ( e.6.c.c.e.4.4.d.f.ip6.arpa) representing the IPv6 address space of the DHCPv6 scope you created in the second exercise of this lab (fd44:ecc6:e322::/64). Note: Now that you created a reverse lookup zone, you need to populate it with the PTR record for LON-DC In the DNS Manager console, expand the Forward Lookup Zones folder and click the Adatum.com folder. 11. In the list of DNS records in Adatum.com, locate the IPv6 Host (AAAA) record representing the IPv6 address assigned dynamically to LON-DC1 and double-click on it. 12. In the lon-dc1 Properties dialog box, enable the Update associated pointer (PTR) record checkbox (if the checkbox is already enabled, first disable it and then re-enable it). Click OK 13. In the DNS Manager console, right-click the newly created reverse lookup zone ( e.6.c.c.e.4.4.d.f.ip6.arpa) and click Refresh in the right-click menu. 14. In the results pane, verify that the new PTR record for lon-dc1.adatum.com has been created. 15. Switch back to the Windows 10 (LON-WIN10) virtual machine. From the Administrator: Windows PowerShell window, try again performing a reverse lookup to resolve the IPv6 address assigned dynamically to LON-DC1 by typing the following command and pressing the Enter key (make sure to replace the <IPv6 address of LON-DC1> with the actual DHCPv6 assigned IPv6 address of LON-DC1, which you identified in the previous exercise):

11 Resolve-DnsName Type PTR -Name <IPv6 address of LON-DC1> -DnsOnly 16. This time, you should receive the response showing the details of the PTR record, including the name, type, TTL (Time to Live), and the corresponding hostname. Important: In order to ensure proper DNSv6 name registration and name resolution in your environment, you should configure the DHCPv6 scope option on the server hosting the DHCP server role (LON-DC1 in this case). In particular, you should specify the list of DNS sever addresses and DNS suffix search list. You will implement these steps in the next task. Task 3: Configure DHCPv6 scope options on the Windows Server 2012 R2 lab virtual machine. 1. On the Windows Server 2012 R2 lab virtual machine (LON-DC1), switch to the DHCP console. 2. In the DHCP console, expand the folder labeled Scope [fd44:ecc6:e322::] Adatumv6 under the IPv6 node, right-click the Scope Options subfolder, and click Configure Options in the right-click menu. 3. In the Scope Options dialog box, on the General tab, select the checkbox next to the DNS Recursive Name Server IPv6 Address List checkbox. In the New IPv6 address textbox, type in the IPv6 address you assigned to LON-DC1 (fd44:ecc6:e322::dc1) and click Add. 4. In the Scope Options dialog box, on the General tab, select the checkbox next to the Domain Search List checkbox. In the New value textbox, type in the domain name suffix assigned to both LON-WIN10 and LON-DC1 (adatum.com) and click Add. 5. Click OK. 6. Switch to the LON-WIN10. On the Windows 10 (LON-WIN10) virtual machine, from the Administrator: Windows PowerShell window, type the following command and press the Enter key: Ipconifg /renew6 Ethernet 7. From the Windows PowerShell prompt, run the following command: Get-NetIPConfiguration InterfaceAlias Ethernet 8. Verify that the DNSServer property displayed in the output returned by the command includes the fd44:ecc6:e322::dc1 entry. Note: You can quickly verify that the newly assigned IPv6 address of DNS server is used to resolve DNS queries by typing nslookup at the Windows PowerShell prompt. This will return the following output: Default Server: UnKnown Address: fd44:ecc6:e322::dc1 which indicate that the DNS server at the IP address fd44:ecc6:e322::dc1 is referenced by default when performing DNS name resolution. To eliminate the UnKnown entry, add the PTR record corresponding to the AAAA record of LON-DC1 fd44:ecc6:e322::dc1 to the reverse lookup zone you created in the previous task of this exercise.

12 Results: After completing this exercise, you will have tested forward and reverse DNSv6 lookups on the Windows 10 lab virtual machine and identified an issue with the reverse lookups. You have resolved this issue by modifying DNSv6 DNS Server settings on the Windows Server 2012 R2 lab virtual machine. You also configured DHCPv6 scope options of DHCP Server on the Windows Server 2012 R2 lab virtual machine to ensure DNSv6 name resolution on all DHCPv6 clients. Note: When you finish this lab select the End Lab link to reset the virtual machines.