A user at a small branch office reports that their laptop cannot reach any website, but the laptop can successfully ping 8.8.8.8. The technician runs ipconfig /all and sees the IPv4 address, subnet mask, and default gateway are correct, but the DNS server field is blank. Which action should the technician take first to restore web browsing?
The laptop can reach 8.8.8.8 by IP address, proving IP connectivity and routing are working. Web browsing fails because domain names cannot be resolved without a DNS server. Manually assigning a valid DNS server address, such as the local router or a public resolver, restores name resolution. This is the most direct first step for the reported symptom.
Why this answer
A successful ping to a public IP address confirms that the laptop has valid IP configuration, a working default gateway, and end-to-end connectivity. The blank DNS server field means the laptop has no way to translate domain names into IP addresses, so web browsing fails. Assigning a valid DNS server address directly addresses the missing configuration and restores name resolution.
Exam trap
The trap here is assuming that a blank DNS server field is harmless because IP connectivity works, when in fact name resolution is required for normal web browsing.