CyberCertPrepNetwork FundamentalsDNS & DHCPEASYFree question
Scenario
A help desk technician receives a call from a remote employee who says 'I can access websites by IP address but not by name. For example, I can open 8.8.8.8 in a browser but www.google.com times out.' The employee connected to VPN 30 minutes ago.
What is the most specific likely cause of this symptom, and what is the first diagnostic step?
- A.The problem is ISP-side DNS filtering; the ISP is blocking DNS queries from VPN-connected clients as a security measure
- B.The VPN tunnel is partially configured; IP routing works but DNS tunnel is blocked. Restart the VPN service to fix
- C.The client's IP address is in APIPA range; the DNS failure is caused by incorrect IP assignment from VPN DHCP
- D.DNS resolution is failing, not network connectivity; the most likely cause is that the VPN's DNS push configuration is not providing a working DNS server address to the client, or the VPN client is not applying the pushed DNS settings. First diagnostic: run 'ipconfig /all' (Windows) or 'cat /etc/resolv.conf' (Linux) to verify the DNS server address the client is using; then test with 'nslookup google.com <dns_ip>' to verify the DNS server responds