Advertisement

Windows 11 Ethernet connects but DNS won’t resolve

Start with the simplest proof tests, then narrow the break to Windows, the adapter, the router, or the DNS server. You’ll see which built-in commands to run and what each result means before you change anything.

Networking 8 min read

If Windows 11 says Ethernet is connected but websites and apps still can’t resolve names, DNS is usually the problem, not the cable. In plain English, your PC can still talk on the network, but it can’t turn names like `example.com` into the IP addresses they need. The fix is to prove whether DNS is failing on the PC, then correct the broken layer: Windows DNS settings, VPN or proxy, security software, the router, or the upstream DNS server.

What the symptom really means

A wired link can be up while name resolution is broken. Your PC may still reach the router and the internet by IP address, but it cannot translate a site name into the numeric address it needs to connect.

That is why Ethernet can look healthy while browsers hang, Outlook stops syncing, or apps say they cannot reach their servers. If ping by IP works but ping by name does not, DNS is the likely issue rather than a dead cable or a full internet outage. If both IP and name fail, the problem is broader than DNS.

A common pattern after a Windows update or driver change is that split: IP connectivity still works, but DNS lookups fail. Some reports describe the issue on more than one interface, not just Ethernet, which points away from the cable and toward Windows or the network’s DNS path.

Prove it is DNS, not the whole network

Start with the simplest split: can the PC reach an IP address, and can it resolve a name?

  1. Open Command Prompt.
  2. Test a raw IP address.
Command Prompt
ping 1.1.1.1

If this works, your PC can reach the internet at the IP level. If it fails, you have a broader connectivity problem, not a DNS-only problem.

  1. Test a hostname.
Command Prompt
ping google.com

If the IP ping works but the name ping fails, DNS is the likely fault. If both fail, look beyond DNS.

  1. Ask Windows which DNS server it is using.
Command Prompt
nslookup google.com

If nslookup fails or shows a DNS server you do not expect, the lookup path is broken even though the Ethernet link is up.

  1. Compare the results.
  • ping 1.1.1.1 works and ping google.com fails: DNS is the likely problem.
  • Both fail: this is not just DNS.
  • ping google.com works after a manual DNS change: the old DNS server or path was the issue.

This is the cleanest way to separate DNS failure from DHCP or link problems. A bad cable, dead port, or broken link usually prevents the IP ping too. DHCP trouble usually shows up earlier, when the PC cannot get a usable address or gateway at all.

Find the layer that is broken

Work from the PC outward.

If nslookup shows an unexpected DNS server, or if you manually set DNS on the Ethernet adapter, Windows may be using a static DNS value that is wrong, stale, or filtered. If one app works and another does not, check VPN and proxy settings next, because they can override DNS or send lookups through a different path.

Security software can also interfere with name resolution, especially if it installs web filtering or a secure DNS layer. If turning off the VPN or proxy makes the problem disappear, you have found the layer that was interfering.

If Windows settings look normal, move to the router. A router can hand out working IP addresses through DHCP while still advertising a bad DNS server. That can happen with router DNS forwarding, custom DHCP options, or a DNS path that is unreachable or filtered.

If the issue affects more than one device on the same Ethernet network, the router or ISP is more likely than the PC. If it happens only on this one Windows 11 machine, focus on the adapter, local DNS settings, or the network stack.

Some reports link DNS failure to a Windows 11 update or a driver change, while IP connectivity still works. In one report, the issue affected every interface on the machine, not just one adapter, so a Windows rollback looked more likely than a cable swap. That does not prove the update caused your case, but it does mean a Windows-side reset or rollback may be worth considering if the timing matches.

Apply the fix that matches the cause

Use the safest fixes first, and stop when the symptom changes in the right way.

  1. Remove any manual DNS override on the Ethernet adapter. Open the Ethernet adapter’s IPv4 and IPv6 settings and switch DNS back to automatic unless you have a clear reason to use static DNS. If you entered a custom server, that alone can cause the failure. If you do not know which path Windows is using now, recheck with nslookup after you change it.
  1. Turn off VPN and proxy settings for a clean test. Disconnect the VPN completely, then check Windows proxy settings and leave them off for the test. If name resolution returns, the VPN or proxy was intercepting DNS.
  1. Flush the DNS cache.
Command Prompt
ipconfig /flushdns

This helps only when Windows cached a bad answer. It will not fix a DNS server that never replies.

  1. Renew the adapter lease if you suspect stale DHCP data.
Command Prompt
ipconfig /release
ipconfig /renew

If the new lease brings back working lookups, the old DHCP state was part of the problem.

  1. Reset the Windows network stack if the local stack still looks stuck.
Command Prompt
netsh winsock reset
netsh int ip reset

Reboot after these commands. Reports from Windows 11 users with DNS-only failures often say this reset, plus a reboot, can restore name resolution when IP connectivity still works.

  1. Try a trusted DNS server only as a test. If the router or ISP DNS looks suspect, set the adapter temporarily to a known public resolver such as Cloudflare or Google DNS. If that immediately fixes lookups, the broken part is usually the router’s DNS forwarding or the upstream DNS path, not your Ethernet cable. If changing DNS does nothing, the fault is probably elsewhere.
  1. Reboot the router if the problem points outside Windows. If other devices on the same network show the same DNS failure, restart the router and check its DNS and DHCP settings. If the problem returns after a router reboot, the ISP path or router configuration still needs attention.
  1. If the problem began right after a Windows update and the failure is broad, consider a rollback or driver check. Some reports tie the issue to a Windows update or a network driver change, and in at least one case the only stable fix was rolling back to 23H2. If the timing lines up and the simple DNS fixes do not help, check the current Microsoft support pages for your build and the PC maker’s current Ethernet or chipset driver source before you keep changing settings.

How to confirm it is actually solved

Do not stop at “the browser opened once.” Confirm the same name lookup works after the fix and after a fresh connection.

Run the same three checks again:

  • ping 1.1.1.1 should work.
  • ping google.com should now work.
  • nslookup google.com should return a normal result and show the expected DNS server.

If those pass, open a few different sites and one app that failed before. If browsing works but one app still fails, that app may have its own proxy, secure DNS, or cached setting. If ping 1.1.1.1 still works but nslookup still fails, the issue is still DNS, not Ethernet.

If you changed DNS servers and that fixed it, keep using that setting only if the router and upstream path stay stable. If the problem returns after a reboot or Windows update, check the current Microsoft support pages for your build and, if needed, the latest Ethernet or chipset driver from the PC maker’s official source. That matters more than guessing at an older driver name or Windows UI path.

Frequently Asked Questions

Should I change DNS servers on Windows 11 if Ethernet is connected but websites still fail?

Yes, but only as a test after you prove IP connectivity still works. If a different DNS server fixes name lookups, the problem is usually your router’s DNS forwarding, your ISP’s DNS path, or a bad server entry on the PC.

What does `ping 1.1.1.1` versus `ping google.com` tell me?

`ping 1.1.1.1` checks raw network reachability, while `ping google.com` also depends on DNS. If the first works and the second fails, your internet path is alive but name resolution is broken.

When should I reset Winsock or the network stack?

Use those resets after simpler checks like removing manual DNS, turning off VPN or proxy settings, and flushing the DNS cache. They help when Windows’ local networking state is stuck, but they will not fix a dead router DNS server or an ISP-side lookup problem.

Sources