A 2.5 GbE Ethernet adapter can show link and even get an IP address while DNS still fails, which means the problem is in name resolution, not necessarily in the cable or the basic internet path. Start by proving whether numeric IPs work and hostnames do not, then check whether the failure is limited to that adapter, Windows, or the router’s DNS settings. The safest fixes are usually to remove bad local DNS overrides, clear the cache, and only then try router or driver changes.
What this problem usually means
When the adapter is connected but DNS resolution is broken, Windows can talk on the network at the link and IP layers, but it cannot turn a name like google.com into an address it can use. That is different from no link, no IP address, or no route off the local network.
The quickest way to think about it is this:
- Link: the port, cable, and adapter are physically up.
- IP: Windows has an address and can send traffic.
- Gateway: Windows knows where to send traffic outside your local network.
- DNS: Windows can translate hostnames into IP addresses.
If DNS fails, websites can look dead even when the adapter status looks fine.
Check whether DNS is broken on the adapter or everywhere
Start by proving the failure with two tests. If numeric IPs work but hostnames do not, DNS is the likely problem. If both fail, the issue is wider than DNS.
- Open Command Prompt or PowerShell.
- Test a numeric IP first.
ping 1.1.1.1If this replies, the basic network path is alive. If it fails, stop treating this as a DNS-only problem.
- Test a hostname next.
ping google.comIf the IP ping works but the hostname ping fails, DNS is the likely fault.
- Confirm which DNS server Windows is using.
nslookup google.comIf nslookup fails, or it shows a DNS server you do not expect, that tells you where to look next. ping is a quick user-facing check; nslookup is better for showing whether the lookup itself is failing and which server Windows asked.
- Compare another connection on the same PC.
- If Wi‑Fi works on the same computer, the problem is probably limited to this Ethernet path or its settings.
- If every network connection on the PC has the same DNS failure, look at Windows settings and the DNS stack first.
- If another PC or another wired device on the same router has the same failure, focus on the router or its upstream DNS path.
Look for local Windows settings that override DNS
A wired adapter can look healthy while Windows, a VPN, or the browser changes where DNS queries go. I’d check the local overrides before touching the router, because that keeps you from changing the whole network to fix a single-PC problem.
First, open the Ethernet adapter’s IPv4 properties and look for manual DNS entries. If someone entered a DNS server by hand and it is wrong, name resolution can fail even though the adapter still shows a normal link. If you do not know why a manual DNS value is there, switch the adapter back to automatic DNS and test again.
Next, check IPv6. Some networks use IPv6 DNS cleanly, some do not, and some drivers behave badly when IPv6 is only partly working. If your network and ISP support IPv6, leave it enabled unless you have a clear reason to change it. If you do change it for testing, change only one thing at a time so you can tell what mattered.
VPN clients, security tools, and some privacy apps can redirect DNS traffic or install their own resolver behavior. Disconnect the VPN fully, stop the app if needed, and retest on the wired adapter only. Proxy settings matter too: a system proxy can make browsers fail in ways that feel like DNS trouble even when the resolver is fine. Browser-level secure DNS or DNS-over-HTTPS can also send lookups somewhere other than the Windows default resolver, so check that if the failure shows up only in the browser.
If only a few hostnames fail and the rest resolve normally, look at the hosts file. A bad entry there can override normal DNS for one site. That is uncommon, but it is one of the few local causes that can make the failure look random.
Verify what the router and driver are handing out
If the PC-side checks do not explain the failure, confirm what DHCP is handing to the adapter. On a healthy wired connection, Windows should receive DNS server addresses from the router or another DHCP server unless you set them manually.
Run this command and check the Ethernet section for the DNS server, gateway, and DHCP details.
ipconfig /allIf the Ethernet adapter shows a DNS server that looks wrong, or it points at the router but lookups still fail, the router may be handing out bad DNS information or failing to forward requests correctly. That is a common trap: the PC looks configured properly because it got the router as DNS, but the router’s DNS forwarding is broken.
If the router is acting as DNS and other devices on the same network have the same symptom, review the router’s DHCP and DNS settings in its admin page. Check whether it is passing along the ISP’s DNS servers, using its own forwarding, or using custom public DNS. The exact menu names vary by router, so check the current manual for your model.
If the problem stays tied to this adapter, look at the driver and Windows networking stack. Dell recommends resetting TCP/IP and DNS settings with netsh int ip reset, ipconfig /release, ipconfig /renew, and ipconfig /flushdns, and it also offers Windows Network reset from Settings. HP also points to driver updates, a clean reboot, and checking startup apps when DNS problems come from software glitches. A stale or buggy driver can break name resolution even when the link stays up.
Try the safest fixes first and know when to escalate
Work from least risky to most disruptive. Stop after each step and retest, because changing several things at once makes it hard to tell what actually fixed the problem.
- Reboot the PC and the router, and wait 30 seconds before turning the router or modem back on. If the whole network seems odd, power-cycle the router first.
- Disconnect any VPN, proxy, or security app that touches DNS, then retest on the wired adapter only.
- Switch the adapter back to automatic DNS if it had manual entries.
- Clear the DNS cache.
ipconfig /flushdns- If the problem still affects only this adapter, reset TCP/IP and renew the address.
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns- If that still does not fix it, use Windows Network reset or reinstall/update the adapter driver. Dell documents Windows Network reset under Advanced network settings, and HP recommends updating the network adapter driver and reinstalling it if needed.
A public DNS server helps when the router’s DNS forwarding is broken or the ISP’s resolver is flaky. It does not fix a bad VPN profile, a proxy, a broken local override, or a driver problem; in those cases it only hides the real cause.
If the adapter still fails after these steps, collect evidence before you contact anyone. Save the output of ipconfig /all, nslookup google.com, ping 1.1.1.1, and ping google.com. Also note whether Wi‑Fi, another Ethernet port, or another PC on the same router has the same failure. Dell’s troubleshooting flow also includes checking whether Ethernet is enabled in BIOS and whether power settings are turning off the adapter, while HP notes that disabling startup apps can help when software is interfering with DNS.
Verify the fix worked
Re-run the same two tests you used at the start.
ping 1.1.1.1
ping google.comYou want the numeric IP test to work and the hostname test to work on the same wired connection. Then run nslookup google.com again and confirm that it returns a usable answer from the DNS server you expect. If hostnames still fail while numeric IPs work, the DNS failure is still active and you should go back to the router, Windows DNS settings, or the adapter driver, depending on which check pointed there.
Conclusion
If the name lookup still fails after the safe checks, do not keep randomizing settings. Bring the saved command output to the router vendor, ISP, or adapter support so they can see whether the break is in Windows, the adapter, or the DNS server path.
Frequently Asked Questions
Why does my 2.5 GbE adapter show connected but websites still fail?
Because link and IP can work while DNS still fails. The adapter may have a valid address and gateway, but if Windows gets the wrong DNS server, or the router cannot forward lookups, hostnames will not resolve even though the Ethernet connection looks normal.
Does changing to public DNS fix the problem?
Sometimes, but only if the failure is in the router’s DNS forwarding or the ISP’s resolver. If a bad manual DNS entry, VPN, proxy, or driver issue is causing the failure, public DNS may hide the real cause instead of fixing it.