Advertisement

Intel Ethernet controller: no DNS resolution fix

If your Intel Ethernet controller shows a live link but names won’t resolve, the problem is usually DNS—not the cable. This walkthrough helps you prove it, then narrow the failure to Windows, the router, the DNS server, or adapter settings.

Networking 10 min read
A desktop PC has an Ethernet cable plugged into its back panel.

If your Intel Ethernet controller shows a live link but websites won’t open, this is usually a DNS failure, not a dead cable or dead adapter. First check whether IP traffic still works while names do not. Then test the DNS server, proxy, VPN, and Windows or Intel adapter settings that can block name lookups. In most cases, you can fix it without replacing hardware, and any temporary DNS change can be undone.

Is this really a DNS problem or just no internet?

If IP traffic works but names fail, you’re likely dealing with DNS rather than a total outage. Start by separating address reachability from name resolution. If you can reach a site by numeric IP or get a reply from a public IP, but www.google.com or another hostname fails, that points to DNS.

A simple split test is ping 8.8.8.8 versus ping www.google.com. If the IP works and the name does not, the Ethernet link is up enough to pass traffic, but Windows is not getting a usable DNS answer. You can make the same check with nslookup. If that fails while IP traffic still works, you’ve narrowed it to DNS or name resolution.

If neither the IP nor the name works, stop treating this as a DNS-only issue. That usually means the problem is lower down, such as the router, DHCP, the adapter configuration, or the network stack.

Before you start

This applies to a Windows PC using a wired Intel Ethernet adapter. You’ll want access to Windows network settings, Command Prompt, and a way to reconnect the PC after a change.

Keep the checks reversible. Do not change static IP settings unless you already know the machine uses them. If you test a different DNS server, write down the original values first so you can restore them later.

If you use a VPN or security software that manages network traffic, plan to disconnect or pause it during testing. Those tools can rewrite DNS paths and make the fault look like an Ethernet problem when it is not.

What this state usually means on a wired Intel adapter

A connected Intel Ethernet adapter with no DNS resolution usually means the physical link is fine, but something above it is broken. The PC can still get an IP address and talk on the network while the DNS server is wrong, unreachable, or being overridden by Windows, a VPN, a proxy, or security software.

In practice, the break is often one of four things. The router may have handed out a bad DNS server through DHCP. The PC may be set to a static DNS server that no longer answers. A proxy or VPN may be intercepting requests. Or an Intel adapter driver or feature may be interfering with the path Windows uses for name resolution.

You can also see this when IPv4 and IPv6 do not agree. Windows may look connected while IPv4 DNS works and IPv6 DNS is broken, or the other way around. Check both stacks before you change anything.

The fastest fixes to try first

Use the safest fixes first, and keep them reversible. In most Windows 10 and Windows 11 cases, I’d go in this order: check the DNS server Windows is using, turn off VPN or proxy paths that may rewrite DNS, test a known good public DNS server temporarily, and only then look at Intel adapter settings if the problem is still there.

  1. Check the DNS server Windows is using.
Command Prompt
ipconfig /all

Look for the DNS Servers line under your Intel Ethernet adapter. If it shows a router address you don’t trust, a stale address, or something you do not recognize, that is the first clue. If the adapter has no DNS server or the wrong one, browsers can fail even though the link light is on.

  1. Turn off VPN and proxy settings before you change anything else.

A VPN client can quietly take over DNS after the link comes up. Windows proxy settings can also send browser traffic through a dead path. Check whether the problem stops when the VPN is disconnected. Also review the proxy setting in Windows and clear any proxy you did not set on purpose.

Settings path
Settings > Network & internet > Proxy

If turning off the VPN or proxy fixes name resolution, stop there and restore only the setting that caused the break. Don’t keep changing DNS if the real issue is a tunneling app.

  1. Test a temporary public DNS server.

If you can edit the adapter safely, set a known good DNS server temporarily on the Intel Ethernet adapter and leave the IP address on automatic unless you already use static addressing. Some Windows support answers suggest testing public DNS values such as 8.8.8.8 and 8.8.4.4 when DHCP looks unreliable. Use that only as a test, and check the provider’s current official addresses before you keep them.

If the new DNS works, your old DNS path was the problem. If it still fails, the fault is probably not the DNS server itself.

  1. Check the adapter and driver for Intel-specific interference.

Open the Intel adapter properties and look for advanced options that affect offload, energy saving, filtering, or vendor-specific features. I would not guess at one magic toggle, because those settings vary by driver and hardware generation. What matters is whether the issue started right after a driver update or a profile change.

If the problem began after a recent change, restore the adapter to defaults and retest. That keeps the fix reversible and avoids stacking changes you can’t easily unwind.

  1. Check whether DHCP handed out the wrong DNS server.

If the adapter is set to obtain DNS automatically, the router may be supplying a bad value through DHCP. That is common when the router’s DNS relay is stuck or the ISP DNS it forwards to is failing. If static DNS fixes the problem, the router or upstream DNS path is the likely culprit.

A quick split test helps here. If another device on the same router also cannot resolve names, the router or upstream DNS path is the better place to look. If only this PC fails, the issue is more likely in Windows, the Intel adapter driver, or a per-device setting such as proxy, VPN, or static DNS.

A hand plugs an Ethernet cable into a desktop PC.

When the router, DHCP, or driver is the real culprit

If the PC gets an IP address and can ping the router, but name lookups still fail, the router or DHCP path deserves a hard look. That pattern says the local Ethernet link is working, but the DNS server handed out by the router may be dead, filtered, or not reachable from your network.

If another device on the same router also fails to resolve names, don’t chase the Intel controller first. Look at the router, its DNS relay, or the upstream DNS settings from the ISP. If only this PC fails, focus on Windows, the Intel driver, proxy settings, VPN software, and any security software that manages traffic.

When the problem stays after those checks, a network stack reset is worth trying. In Windows, that reset rebuilds parts of the TCP/IP stack and Winsock, which can clear corrupted resolver state or broken socket catalog entries. It does not replace the driver, erase your files, or fix every DNS problem, so I’d treat it as a repair step after the simpler checks, not the first move.

If you want to proceed, use the built-in reset tools, then reconnect and recheck DNS. If you had static IP settings, VPN settings, or custom DNS values before, write them down first so you can restore them after the reset.

Command Prompt
netsh winsock reset
netsh int ip reset
ipconfig /flushdns

If the reset does not help, move to the driver next. Reinstalling or updating the Intel Ethernet driver is worth doing when the issue began after a driver change, after a major Windows update, or after a firmware or adapter-profile change. Use the system or motherboard vendor’s driver first if they provide one for your hardware, then compare with Intel’s current package if needed. Check the current release notes and support pages before you install, because driver behavior can change over time.

After the fix, restore or recheck these items: the original DNS server setting, proxy state, VPN connection, adapter profile, and whether DHCP is back on if you had switched to static DNS for testing. Then repeat ipconfig /all and a name lookup so you know the machine is using the path you intended.

A desktop PC is connected to a router by an Ethernet cable.

Verify the fix

A working fix should make both IP and name lookups succeed. Open a browser and load a few different sites, then repeat the same split test you used earlier.

Command Prompt
ping 8.8.8.8
ping www.google.com
nslookup www.google.com

You want the IP test and the name test to succeed, and nslookup to return an answer instead of timing out. If the name lookup works after you change DNS or disable a VPN or proxy, the broken link was in name resolution rather than the Ethernet controller itself.

If the browser works but nslookup still fails, check whether a VPN, proxy, or security tool is still active. If only one site fails, the issue may be that site’s DNS record or a cached entry rather than your adapter.

When to stop and switch branches

If IP traffic fails too, stop focusing on DNS. That points to a broader connectivity problem, such as the router, DHCP, the adapter link, or the Windows network stack.

If DNS works on the same PC over another network but not on this router, the router or upstream DNS is the real fault. If the problem only happens after a driver update, adapter profile change, or security software change, restore that last change first instead of chasing random fixes.

Frequently Asked Questions

If ping works by IP but websites still fail, what should I check first?

Check DNS first, then proxy and VPN. If `ping` to a public IP works but `ping` or `nslookup` for a hostname fails, the Ethernet link is probably fine and the break is in name resolution, not the cable or the Intel controller.

Can the router cause this even if my Intel Ethernet controller shows connected?

Yes. A router can hand out a bad DNS server through DHCP or fail its DNS relay while the link stays up. If other devices on the same router also fail to resolve names, the router or upstream DNS path is the better place to look.

Should I reset the network stack right away?

No. Try DNS, proxy, VPN, and adapter checks first because they are easier to undo. Use a network reset when the problem survives those checks or after a bad stack change, and be ready to reapply any manual IP or DNS settings afterward.

Sources