You have been asked to troubleshoot a specific network problem that has occurred soon after a major implementation of IPv6 in the network. According to the problem report, some of the hosts on the network have network access, but their web browsers are not able to resolve the URLs that are entered. The network hosts experiencing this problem are able to ping other hosts on a different network only via IPv6 addresses. It has also been reported that the hosts on the other network segment can resolve their URLs without any problems. All network hosts obtain their IPv6 addresses via stateful address autoconfig. Discuss your perspectives on what may be the reasons causing the problem here. What might be some areas that you want to explore further in order to determine the cause of the problem? What Wireshark display filter could you use to investigate and determine the network problem? Currently, I think that I am on the right track. Boot sequence; discovery, offer, request, ACK. The use of a non-valid lease could prevent communication and having an incorrectly set renewal time or rebinding time could also present communication errors. Troubleshooting other critical areas used for successful communication would be reviewing how the RA Flags used for obtaining an IP address are set up, ensuring that all DHCPv6 DNS records are set up to dynamically update. I would begin looking at each domain controller to ensure that the correct DNS setting has been set up on its stack with tertiary set to loopback. Then double check that a reverse lookup zone is configured for the IP range on the domain controllers. I would also take a look at the binding order that is set up with the network stack and check to see if the primary NIC is set at the first network interface. The ping command can be used as a troubleshooting tool for verification that translations processes are working properly/