Windows 11 Wi-Fi Connected but No Internet: Safe DNS Checks

If Windows 11 shows Wi-Fi connected but no internet, first establish whether the problem affects one app, your PC, or the whole network. Then inspect the IP configuration and test DNS before changing anything. A Wi-Fi connection establishes a local wireless link; it does not prove that your router, internet service, DNS, and browser are all working.

This guide uses Windows 11 settings and current Microsoft Edge terminology. Start with the checks below and stop when normal access returns. There is no need to change every setting or run a bundle of reset commands.

What should you prepare before changing network settings?

Save open work and record any manual IP addresses, DNS servers, proxy details, and VPN settings. Have your Wi-Fi password available before reconnecting or removing a saved network. Reading settings and running the diagnostic commands below do not erase documents or browser data; some repairs can interrupt the connection.

On a work or school device, keep organization-provided settings and involve IT before changing them. Use a local session rather than a remote connection for actions that disconnect the network. Administrator permission may be needed for repairs, although the initial read-only commands normally work without elevation.

1. Is the failure limited to an app, your PC, or the network?

Open two unrelated, familiar websites and try another internet-dependent app. On a phone or second computer, test the same Wi-Fi network. Temporarily turn off the phone’s cellular data during this comparison, then restore it afterward so a mobile connection does not hide the Wi-Fi problem.

Microsoft explains that its Network Connectivity Status Indicator uses probes to assess access. A blocked probe can produce a warning even when some internet traffic works. Keep the actual application results as evidence rather than trying to fix the icon by disabling connectivity checks.

On hotel or public Wi-Fi, use the network’s sign-in notification or its official instructions to complete the access portal. Do not bypass certificate warnings or enter credentials into an unfamiliar page. If every device fails at home, check the provider’s outage information using another connection.

A normal router restart briefly disconnects everyone using it. Use the manufacturer’s restart procedure when appropriate; the recessed factory-reset button can erase configuration and is a different operation.

2. Does the Wi-Fi adapter have a usable IP configuration?

Search Start for Command Prompt, open it, and run:

ipconfig /all

In the active Wireless LAN adapter Wi-Fi section, or the equivalent named Wi-Fi adapter, note the IP addresses, Default Gateway, DHCP Enabled, and DNS Servers. Ignore disconnected adapters. VPN and virtual adapters can have separate entries. Microsoft’s ipconfig reference documents this read-only configuration display.

• An automatically assigned IPv4 address beginning 169.254: commonly indicates that Windows did not obtain a DHCP lease. Investigate address assignment and the local network before treating this as only a DNS problem. IPv6 connectivity may still differ.
• No expected gateway: check the configuration required by your network. Do not copy a gateway address from an unrelated tutorial.
• A DNS server is listed: that is a configuration value, not proof that it can answer queries.

Optionally type ping, a space, and the gateway address shown for your actual connection. Replies show that this local endpoint answers ICMP; they do not prove internet access. A timeout is inconclusive because some devices or firewalls do not answer ping. Keep the firewall enabled.

3. Can DNS resolve a name, and would clearing its cache help?

DNS, the Domain Name System, translates names such as www.microsoft.com into network addresses. Run this read-only lookup in Command Prompt:

nslookup www.microsoft.com

Then repeat the lookup using the hostname of a failing site, without https:// or a page path. According to Microsoft’s nslookup documentation, omitting a second server argument uses the default DNS server.

Microsoft’s DNS-client troubleshooting guide notes that nslookup bypasses the Windows DNS client cache. If direct lookups succeed but an app may be using an old cached answer, open Command Prompt with Run as administrator and run:

ipconfig /flushdns

Windows should confirm that it flushed the resolver cache. Close and reopen the affected app, then retest. This clears temporary DNS records; it does not delete cookies, passwords, documents, Wi-Fi profiles, or your configured DNS servers. It also cannot repair an unreachable router or DNS server.

4. Should DNS or IP assignment be automatic?

On an ordinary home network, DHCP normally supplies the addressing information. A stale manual DNS entry left by an old configuration can interfere with access. Preserve intentional settings for business networks, filtering services, or specialist equipment.

1. Open Settings > Network & internet > Wi-Fi and select the connected network’s properties.
2. Find DNS server assignment and select Edit. Record the existing mode, addresses, and encryption options.
3. If the manual configuration is unintended, choose Automatic (DHCP), select Save, and retest. This returns DNS selection to the network’s configuration.

If Windows reports that DNS settings for all Wi-Fi networks override the individual network, inspect Wi-Fi > Hardware properties as well. Record any adapter-wide setting before changing it.

Check IP assignment separately. Change it to Automatic only if the network is supposed to use DHCP and a manual IP configuration is incorrect. Doing so replaces the static address, gateway, and related settings and can interrupt access. Restore your recorded values to undo the change.

Microsoft’s TCP/IP settings guidance recommends DHCP where supported. Windows 11 also exposes DNS-over-HTTPS options for supported configurations; Microsoft notes that those Settings controls are unavailable in Windows 10. Preserve an intentional encrypted-DNS policy rather than switching encryption off as a general repair.

5. Could a proxy, VPN, or Edge setting explain the difference?

Open Settings > Network & internet > Proxy. Look for a manual proxy or setup script you recognize. Microsoft’s proxy guidance explains that organizations may require these settings.

On a personal PC, if an obsolete manual proxy is the suspected cause, record its address and port, turn that specific setting off, and retest. Restore it if the test does not help. Do not remove an organization’s script or required proxy.

If you use a personal VPN, a brief comparison while disconnected can help, provided policy permits it. Disconnecting changes traffic routing and removes the VPN’s tunnel protection; internal resources may stop working. Some VPNs intentionally block traffic with a kill switch. Reconnect afterward and use the VPN provider’s guidance if the problem follows that connection.

What if only Microsoft Edge fails?

Current Edge documentation places Use secure DNS under Settings > Privacy, search, and services > Security. Inspect whether you previously selected a custom provider. Restore the previous working or current-provider configuration if that custom choice is the issue; record the original choice first.

Microsoft’s Edge privacy documentation explains that a specifically selected secure-DNS provider does not fall back to ordinary DNS when its secure lookup fails. Edge can therefore behave differently from nslookup. InPrivate uses the originating profile’s secure-DNS configuration, so an InPrivate test does not isolate that setting. Managed settings should be handled by your administrator.

6. When should you reconnect, restart, or reset the network?

After recording the diagnostic results, save your work and try reconnecting Wi-Fi or restarting the PC. If available, compare with Ethernet or another trusted network. Ethernet success points toward the wireless path or its configuration, but it is not a conclusive hardware diagnosis.

Microsoft directs Windows 11 users to the Network and Internet troubleshooter in Get Help. Its Wi-Fi troubleshooting guide treats Network reset as a final option.

Before resetting, retain configuration details and any VPN setup materials. Network reset removes and reinstalls adapters and resets their settings. You may need to reinstall or reconfigure VPN clients and virtual switches; network profiles may become Public.

For Windows 11, use Settings > Network & internet > Advanced network settings > Network reset > Reset now, confirm, and allow the restart. Windows 10 uses the older Network & Internet > Status > Network reset route.

If the problem persists, give your ISP or IT support the Windows build, Wi-Fi adapter model, time of failure, affected apps, comparison-device results, and DNS error wording. Microsoft’s advanced wireless guidance emphasizes preserving evidence before resets and driver changes. Share network details privately with support rather than posting complete configuration output publicly.

The practical success check is that multiple sites and the affected app work after reconnecting, with required VPN and security settings restored. A DNS lookup, a changed icon, or one successful page load alone is a narrower result.